Bug Stomp

More language from nowhere:

Daeya: I like ezzer.
Simulo: NewAdam is sometimes hard to come by.
Daeya: Hmm....
Simulo: What do you mean by 'we'?

The first of those replies from Simulo is a response to "I like," and it uses a postkey. The second is his (zero-rank) response to an unmatched phrase with the word "we" in it.

Skysaw, my tests show those working correctly. Try the following in Debug: "Those dogs like this. That was cool." The word "those" is marked as an adjective, while "this" and "that" are properly marked as pronouns.

Athyrius, did you get logged out immediately after that?

Feyz: You must have a pop-up blocker in place. I've heard a particular virus could cause that too, but it's not the Forge.

Feyz-- I had a lot of problems with IE6 before, too.

I've been having repeated incidents of when a bot says "hmmm" to Julie, she replies to the keyphrase "you are (adjartnoun)," plugging in some random (key1). In a recent chat she interpreted "hmmm" as "You are full."
Kinda makes ya say "hmmm."

@Prof. & Shadyman
Thanks. Gotta check for that virus (I'm experiencing some other funny problems recently too). I'm sure it's no popup-blocker.

ezzer-- Maybe it means "mmm"?

Prof--
About that thing on the front page that sets focus to the login name textbox.. It's a great idea and all, but I find it's really annoying, like when you get the browser to stop loading and click to change the address and start typing, it ends up in the username box instead. Also, on this lovely slow work computer, I clicked and typed in my username, (tab), password, and right as I went to type my password in the password field, it moved the cursor back to the username field *blush* I'm glad no one saw!

ezzer- I tried "hmmm" several times in Debug to Julie and it worked alright. In what kind of chats are these non-sequitors happening? Guest chats, User chats? Bot-to-Bot chats?

Professor,

I guess I'm just having a problem with this/that/those/these being marked as an adjective in any case. I guess it's technically correct, but doesn't help at all in matching on (adj). For example, not having a more specific match, my bot might return the following for (adj): "Not as (key1) as you'd think!" -- Doesn't look too good when you get something back like "Not as that as you'd think!"

Just one example, but I can't think of a situation where you'd really want to get one of those words when seeking an adjective.

I see your problem, but there's cases where it's necessary to have them as adjectives. Here's one..

Message: "Do you like that dog?"
Keyphrase: do you like (adjartnounprep)
Response: I'm crazy for that dog!

xCOMMAND IMPROVEMENT!
I've just made several big improvements to xCommand, which solves every case on my large list of "things that are not commands". It makes sure of the following things before triggering xCommand: That there are no words in the sentence without a linkgrammar link to another word, that no words are respelled, that no words are unknown, that no words are in the "not-a-command" list, and that the command is not a third person statement.

Yay! Thank you, Professor!

Yay for the xcommand! Thanks, prof.

I think I've solved my this/that problem, but I've found another...

Consider having the keyphrase (this|that) (noun)
Words that can only be nouns will hit this, ie "that apartment." However, words that can be more than one type will not hit it, ie "that dog" (n, v). The weird thing is that even if I add in another keyphrase (this|that) (verb), the phrase "that dog" will not match either of them. It is listed as only n,v in debug.