{ "attachments": [], "comments_archived": true, "date": "2005-06-24T04:27:39.000Z", "layout": "post", "title": "decafbot update & FAQs", "wordpress_id": 657, "wordpress_slug": "decafbot-update-faqs", "wordpress_url": "http://www.decafbad.com/blog/?p=657", "year": "2005", "month": "06", "day": "24", "isDir": false, "slug": "decafbot-update-faqs", "type": "entry", "postName": "2005-06-24-decafbot-update-faqs", "html": "

So, decafbot has been an interesting experiment so far, especially for a 20 minute hack I didn't think would actually work. So, I think I might try to keep this bot running and tinker some more.

\n

First thing, it looks like the original Infobot is abandoned, but there's a (slightly) more active fork named Flooterbuck. I used to be a more active participant in #perl, so I used to be more up on these things, but oh well. Eventually, I could explore another bot built from POE parts, or leave Perl altogether for a Python-based bot. For now, though, decafbot has been upgraded with Flooterbuck.

\n

And, you should know when you talk to decafbot that your conversation may be monitored for training and quality assurance purposes. I noticed a few people using more AIM-speakish language than the bot's probably used to seeing in the more peer-enforced literacy zone of #perl, so I might work in a few snarky factoids toward that end.

\n

That, and many people seemed to have trouble understanding what to say to the bot. It occurs to me that most people learned how to interact with the #perl infobots by example--since most queries occurred in public, the more astute newbies in the channel would eventually pick up on what the bot did by watching regulars. However, this instance of the bot is pretty much all-private all-the-time, so it's a bit different.

\n

Flooterbuck seems to have a bit more documentation around it, so maybe people dropping in to chat will have a little more success. In any case, more tinkering to be done...

\n

Archived Comments

\n\n\n\n
\n\n\n", "body": "So, [decafbot][] has been an interesting experiment so far, especially for a 20 minute hack I didn't think would actually work. So, I think I might try to keep this bot running and tinker some more.\r\n\r\nFirst thing, it looks like the original [Infobot][] is abandoned, but there's a (slightly) more active fork named [Flooterbuck][]. I used to be a more active participant in #perl, so I used to be more up on these things, but oh well. Eventually, I could explore another bot built from POE parts, or leave Perl altogether for a Python-based bot. For now, though, [decafbot][] has been upgraded with [Flooterbuck][]. \r\n\r\nAnd, you should know when you talk to [decafbot][] that your conversation may be monitored for training and quality assurance purposes. I noticed a few people using more AIM-speakish language than the bot's probably used to seeing in the more peer-enforced literacy zone of #perl, so I might work in a few snarky factoids toward that end. \r\n\r\nThat, and many people seemed to have trouble understanding what to say to the bot. It occurs to me that most people learned how to interact with the #perl infobots by example--since most queries occurred in public, the more astute newbies in the channel would eventually pick up on what the bot did by watching regulars. However, this instance of the bot is pretty much all-private all-the-time, so it's a bit different.\r\n\r\n[Flooterbuck][] seems to have a *bit* more documentation around it, so maybe people dropping in to chat will have a little more success. In any case, more tinkering to be done...\r\n\r\n\r\n[flooterbuck]: http://flooterbuck.sourceforge.net/\r\n[decafbot]: aim:goim?Screenname=decafbot&Message=help+index\r\n[infobot]: http://www.infobot.org\r\n\r\n
\r\n

Archived Comments

\r\n \r\n \r\n \r\n
\r\n ", "parentPath": "./content/posts/archives/2005", "path": "2005/06/24/decafbot-update-faqs", "needsBuild": true, "prevPostPath": "2005/06/23/quick-mind-interface-thoughts", "prevPostTitle": "Quick mind interface thoughts", "nextPostPath": "2005/06/24/locking-down-mac-os-x-for-intel", "nextPostTitle": "Locking down Mac OS X for Intel" }