Bug Stomp
Upgrades and changes sometimes have unpredictable results, so post your bugs and glitches in here and I'll get out my trusty wrench and get to fixin'!
Posts 186 - 197 of 8,683
Posts 186 - 197 of 8,683
Roget- not a bit. I just add it to the list. I added 7 of those that werent on there. I'm an apostraphe-dropper myself, so this should improve things. If you can think of any others, I'll check the list for them.
Rahz- Ah yes. I fixed that. That was a function in place to prevent people from changing the Context of the x Keywords, but xnomatch doesnt fall into that category. You can edit that field now.
The login page will shortly remember your user name.
Rahz- Ah yes. I fixed that. That was a function in place to prevent people from changing the Context of the x Keywords, but xnomatch doesnt fall into that category. You can edit that field now.
The login page will shortly remember your user name.
Re/ contractions
How about I've and you've, for ive and youve. You could also add weve and theyve, although they're not very common.
On a related subject, how about "cannot" and "can not". They're both correct, as far as I know, yet they aren't recognized as synonyms.
Also, I'm sure you noticed this, but a list of contractions is popping up in the chat windows.
How about I've and you've, for ive and youve. You could also add weve and theyve, although they're not very common.
On a related subject, how about "cannot" and "can not". They're both correct, as far as I know, yet they aren't recognized as synonyms.
Also, I'm sure you noticed this, but a list of contractions is popping up in the chat windows.
Yah, I saw that. It's gone now.
Good suggestions. I've added them, including cannot->can not. So there's no need to use cannot as a Keyword now.
Good suggestions. I've added them, including cannot->can not. So there's no need to use cannot as a Keyword now.
I don't know if this is a good idea, but tell me what you guys think:
We have x-introduce, x-initiate, x-goodbye, x-hello and x-none.
How about a new one called x-terminate? (no pun intended)
I don't know if this is possible, but could x-terminate be created that would perform the same function as x-gottago? This would work in the same way except the bot doesn't log off. It closes a specific chat window of one conversation.
We have x-introduce, x-initiate, x-goodbye, x-hello and x-none.
How about a new one called x-terminate? (no pun intended)
I don't know if this is possible, but could x-terminate be created that would perform the same function as x-gottago? This would work in the same way except the bot doesn't log off. It closes a specific chat window of one conversation.
I think that would appear to many as a bug. A Bot stops responding without any reason- people will thing something is wrong. Plus x-words indicate that a Response is coming.
On the compounds, is there a way you can add a checkbox so we can designate which lines work well in them and which don't. Lines like "If you have to ask..." don't look too good with a following statement.
Not yet, but that might be a good idea. Does anyone else have bad compounds coming up (aside from a few repetition errors earlier on)? Or is it generally working well?
Re/ compounds --
So far so good. I've seen a few "clunkers", but generally they seem to work well. I need to rephrase a few of the xnone's to accomodate the new process.
I was going to suggest any response that has a possible SEEK should not get a compound tacked on, as that could potentially ruin the nested contexts we've all worked so hard on. That would also allow people to effectively designate certain responses as non-compounds, simply by specifying a Seek response.
Then again, I have yet to see a compound come up on a potential Seek answer, so maybe it already works that way.
So far so good. I've seen a few "clunkers", but generally they seem to work well. I need to rephrase a few of the xnone's to accomodate the new process.
I was going to suggest any response that has a possible SEEK should not get a compound tacked on, as that could potentially ruin the nested contexts we've all worked so hard on. That would also allow people to effectively designate certain responses as non-compounds, simply by specifying a Seek response.
Then again, I have yet to see a compound come up on a potential Seek answer, so maybe it already works that way.
Don't know if it's a bug or an observation. The synonym detector works too damn well. I figured "pregnant" and "yearn" were both unique words. But no. Words evoking size and ripeness seem to call up the pregnant response, and "long" brings up the "yearn" one. Makes for some very botlike chats.
Really? I'll have to look into that. My initial impression was that the synonym system was very specific. There are a few words in WordNet that are crossed with the wrong thing. I think sneeze is a synonym for the American Crow, but I havent seen many other cross-overs. Does anyone else see the synonym system acting too broadly?
» More new posts: Doghead's Cosmic Bar