Bug Stomp

It's called Al Gore syndrome.

That's easier said than done. There's no way right now for the AI Engine to determine that the first "you" is referring to Lunar22, while the second "you" is referring to the listener.

LinkGrammar might help with that, but the one guy who can help me over there answers my questions with "Learn C". All he had to do was to send me a snippet of code, but he says instead "Learn C". Bastard.

pwahaha That's funny

I'm going to be learning a little C++ next semester.

I tried to answer your C question, but like I said, my understanding is limited. Hopefully the links I sent yoou will enable you to learn just enough of it to read more of what you're working with.

There is something rotten in the state of Denmark:

HTTP-error 500 (have the Dutch version, so hope it's correct) popped up twice, both in bot-bot and hum-bot

and always when I expect an interesting answer
[Error removed. Please place spaces in long errors]

That's precisely the bastard error. The telling sign is this in the middle:
"Process 8 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process."

I thought I fixed it for good a couple hours ago.. but I just saw it again. CURSES!

Please place spaces in long errors... Ok, I admit, I am not the brightest PC expert... But if you put in spaces, doesn't that make it even longer? And where exactly do I put spaces?

Long strings of text wont wrap unless you put a space in them. That makes the message box longer than usual.

That multiple logins by bots thing is happening again, and from the look of things it is impacting conversations.

Not sure of a bug, but popped up in chat window during bot-bot conversation, which seems to have stopped afterwards.
<!-- Adjust Synonym List to avoid common mista