CleverBlogName

PlonieBot is in the early stages of development

Can pull content from Plone nets, but can’t yet put it back. This, obviously, is the most obvious weakness of the tool. Code will be open sourced.

Python based. Python is allegedly the easiest way. Wave IDs are hard, which is why two-way stuff isn’t working so well yet.

User creates a wave and adds ploniebot@appnet.com to the wave; this acts as the gateway.

“Code for getting the content and adding to the wave is trivial—a few lines and you’re done.”

Plone is not the only system that utilises XMLRPC - Drupal, Joomla, and Wordpress all support, so other bots could use the same process.

Another one; OpenAusBot. Offers JSON or XMLRPC APIs, allows member/Hansard lookups.

A wave can respond with answers to queries as part of the conversation. You can create a wave for OpenAusBot, as who your rep is, get a response, ask questions about their Hansard speeches (for example), and have it auto-reply with relevant information. This opens up the idea of, for example, rich conversations with clients about Plone work for them, or other extranetting of conversations about information.

Independent Wave clients; FedOne, PyGoWave and others. Native clients. This is the stuff I want before committing to Wave; I wasn’t interesting in handing all my email to servers run by an advertising company in the US, and Wave is no different. Likewise I can imagine regulatory conniptions if the Bank got Wave wrong, and local servers may have something to do with that.

The current speaker is talking about the problems of handling poorly behaved bots—is this where I say “China”?

I agree with the ideal Wave server James Purser is presenting as his ideal—integrating email and groupware functionality while working as an independent federated—or non-federated—node.

Watching an Emacs Google Wave client at the LCA2010. Madness.