Bug Stomp

In order to prevent these problems, might it be a good Idea to keep transcripts only available during a week?
Maybe it gets too crowded now?

Ooh yeah NT will do that to yah

well it is been frustrating lately to try to chat and work on your bot in the debugg mode cause you get error messages almost immediatly after you send me the message.

The server keeps logging me out and I have been actively doing something.

It might be better to stop working on your bots til everything is resolved, might be useless otherwise

We have determined that the new server is unworthy of assimilation.

Okay, conversations are sort of working now; at least they don't get stopped after the greeting. But Sage is trying for a record I think.

Cancel that. Everything's not working again.

But as of about 5pm things seem to be golden. It looks like my ultimatum with the server company worked. There was two large scripts that were helping to trigger the error- one was me reading in pronunciation data into the AI Engine, and the second is the Link Grammar linkings. The former has been completed, the latter I'll wait a day or two to try again.

So go, have fun as before. Let's hope LinkGrammar can load up, and then let's hope it's as fast as it is supposed to be.

I guess the thing I'd like to see fixed most right now is this "you" glitch in gossip:
"My feelings for lunar22 is like a heated up motley of hatch nickel, lunar22 know what I mean?"

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.