Yardbird should support xmpp as well as irc

[Space Hobo]

What it says. The response types should map to whatever twisted uses for jabber, but otherwise it should be a simple clone of bot.py (and these things ought to be renamed/refactored etc).

[Space Hobo (spacehobo)]

Just collecting odd notes here:

 http://xmpp.org/extensions/xep-0045.html

XMPP messages at their core are "message", "presence", or "iq". IQ is a query/response dealio, and requires maintaining state on at least one end (rather like DCC I suppose).

Jabber MUC is descended from Jabber GroupChat 1.0 in a backward-compatible way, so you get these XML documents that look like nested "domish" dictionaries in twisted, and the MUC ones have an "x" tag inside that holds all the stuff that gc1.0 couldn't do.

Wokkel looks interesting, but we'll likely be implementing our own JabberRequest and JabberResponse objects anyway, which should encapsulate the details of the events a little better. Ideally I'd like for the basic message/action/notice type events to appear identical, so that a module can work for both.

[Space Hobo (spacehobo)]

http://thetofu.livejournal.com/73544.html shows the wokkel stuff

[Space Hobo (spacehobo)]

"Jabber supports the IRC convention of allowing "emote" messages. These allow a person to send a message that looks like an action (such as a stage direction) rather than a quote. Your client can recognize an emote message by the prefix "/me "; this should be replaced with the person's [nick]name before displaying it."

So I guess that's encoded in the payload, then. Bizarre.

[Space Hobo (spacehobo)]

Just to keep spamming anyone subscribed, I got the above from http://www.akeni.com/en/support/jabberclientcheatsheet.php

[Space Hobo (spacehobo)]

The "roster" presence spams actually help us, since they map rather nicely to the way we already keep track of oper status in IRC by doing WHO requests every time we notice a join, part, or mode change. Should work well with the @require_chanop decorator stuff.