[Updated] Improve Jabber/XMPP implementation on Drupal 6

(Note: This proposal has been submitted)

// Idea Summary

The idea is to improve, and implement a feature-rich XMPP API (Extensible Messaging and Presence Protocol) in Drupal 6. Such an API will allow communication between Drupal and other XMPP clients. This will give an alternative on how Drupal systems can notify users of changes/updates. Users might also remotely interact with Drupal, using IM. A generic API will also benefit the Drupal universe as other modules can hook into XMPP when needed.

// Project Details

The development of the project can be divided into two broad sub-parts:
1. Communication from Drupal to users with XMPP clients.
2. Communication from XMPP clients to the Drupal system.

(I know that a previous XMPP API already exists for Drupal 5.x. I shall refer to that code, improving at places and re-writing at others, as and when needed. Some other open source libraries might also be used, they are mentioned later. But, no external XMPP software will be used, it will be a pure PHP/Drupal codebase.)

Drupal-to-clients: I shall not write a full XMPP server in PHP, as time is a constraint. Instead, I shall implement an "XMPP bot" in PHP. This bot will play the partial role of a server, by "talking" with other XMPP clients. By this way, Drupal can easily contact clients when needed. Hooks will be implemented for other modules to connect into. Some features will be inspired from the Druplicon bot also.
Clients-to-Drupal: One way I see this is remotely updating content on a website running Drupal. This method will have to include security so that users are verified before any site updates. The bot will have to automatically authorize "friend requests" so that clients can easily connect to Drupal. Administrative work can be done on the site using small commands sent through IM, though a permissions system will be made for this.

I shall be using and consulting other code libraries, some of which are Jatter (ref. http://sourceforge.net/projects/jatter), xmpphp (ref. http://code.google.com/p/xmpphp). Even though these are pure PHP libraries, I shall properly "drupalise" the code so that it blends in with the rest of the system.

// Timeline (estimated)

I have estimated a development timeline, as follows:
April 21 to May 20: Announce my idea in the Drupal and XMPP community, discuss the pros and cons of various ways of implementation, get familiar with project system and CVS on drupal.org. I will also get familiar with how XMPP works internally. I am taking into account my 4th semester exams during this period. In short, ensuring I can rocket off as soon as Kick-off day comes.

May 20 to June end: Build the basic bot frame, test it with community help. Drupalise the code well, implement necessary hooks. Pings can be tried out with the help of other modules. Ensure constant improvements from feedback of the community.

Till 20th July: Test XMPP client to Drupal connections, including security issues and permissions. Test updating basic content remotely, test some intuitive features (like switch to site-offline with one IM). I shall ship the module with some functions, others can be suitably added by hooking. Again, monitor for community responses.

Till August 10: Get everything ready for public release, clean up code, strengthen up weak points, do necessary documentation. Hope everyone is happy, and life is good :)

// Advantages

Some of the advantages I see (and some suggested by the community) are:
- Remotely update content on a Drupal site, like a micro-blog as in twitter.com
- Inform users of site updates, internal Drupal messages etc. This can be linked up with actions.module also (now part of core)
- Small administration tasks (like switching to maintainence mode) can be done via a single IM to Drupal.
(These are practical uses of the API, but apart from these, developers might see more uses, due to the generic nature of this API.)

walkah and me discussed this on IRC, and he is interested in mentoring this project.
Suggestions and improvements to this proposal are very welcome. Thanks!

PS: A practical implementation of this idea can be a Twitter like site. This module, along with the mailhandler.module as easily be used to whip up something like Twitter. Just a friendly thought I had for a long time :)