[Reporters: Nicolas Vérité and Peter Saint-Andre]
For those who love round numbers, welcome to the tenth edition of the XMPP Roundup, our semi-regular review of news and events in the XMPP community. Since our last roundup on May 11, here’s what’s been happening…
Google has announced the existence of Google Wave, an early-stage technology for real-time interaction that will incorporate aspects of IM, email, wikis, and other collaboration techniques. The technology for federating different Wave instances is pure XMPP, so the developer community is watching this project quite closely.
Minbif is an IRC gateway to IM networks which lets the user connect to Jabber (and many proprietary legacy IM systems), through IRC command lines. It is release under the GPLv2 license, in version 1.0alpha as the time of this writing.
Nolan Darilek has announced the development of Utterance, an XMPP microblog transport, written in Ruby under a BSD license.
Hemlock is an opensource soon-to-be-released Flash XMPP framework.
http://askme.im/ has a set of XMPP bots that cover quotes, jokes, movie reviews, stock prices and daliy horoscopes, and much more…
Jabbim’s URL shorting service
Members of the XMPP community have started work on two new initiatives: an open framework for XMPP protocol testing and a website for information about the XMPP network. To participate, join the email@example.com discussion list or the firstname.lastname@example.org discussion list, respectively. Expect to see more work on these projects in the coming months!
The big news here is that the core Jingle specifications have finally advanced from Experimental to Draft status (version 1.0)! We’ll post more about this in the near future. The specs that have moved forward are:
- XEP-0166: Jingle
- XEP-0167: Jingle RTP Sessions
- XEP-0176: Jingle ICE-UDP Transport Method
- XEP-0177: Jingle Raw UDP Transport Method
Another important specification to advance from Experimental to Draft is Roster Versioning. This technology will make it much more efficient for IM clients to log into XMPP servers, since the server can inform the client if the user’s contact list has not changed since the client last logged in (or send a small diff if it has changed). This is especially important in mobile applications such as cell phones and PDAs. The roster versioning technology is one of the mobile optimizations we are working on, and will be incorporated into the revisions to RFC 3921 within the IETF’s newly re-formed XMPP Working Group.
In addition, the XMPP Council has been working to advance more XEPs from Draft to Final. The latest specification to be so honored are:
Finally, the Council has also been performing some “spring cleaning” by officially obsoleting XEP-0003: Proxy Accept Socket Service, XEP-0011: Jabber Browsing, XEP-0022: Message Events, XEP-0023: Message Expiration, XEP-0025: Jabber HTTP Polling, XEP-0090: Legacy Entity Time, and XEP-0091: Legacy Delayed Delivery.
Again, 2009 seems to be a very active year for XMPP technologies.