It was noted on the Google Code Blog that microblogging site Jaiku will be released as Open Source software. The code will target the Google App Engine platform, so that people who want a microblogging site on GAE can build one almost instantly.
Interestingly, the announcement included this sentence:
The new Jaiku Engine will include support for OAuth, and we’re excited about developers using this proven code as a starting point in creating a freely available and federated, open source microblogging platform.
There’s a great opportunity here for Jaiku and its new Open Source clones to join the existing OpenMicroBlogging network. (I suspect that the reference to OAuth, which forms the basis for OMB, might be referring to that.) But it also seems clear that they’ll be looking to Python hackers in the outside community to do the implementation.
There are dangers, too, here. One is that Jaiku creates a custom protocol, effectively cutting off the site and its clones from the OMB network. This would be problematic; it’s unlikely that two competing protocols will get much traction. Another is that the OMB code for the Jaiku engine is implemented in a patch, a fork, or a difficult-to-install plugin, meaning only a minority of Jaiku installations are OMB-connected. I’d love to see the code either part of their core, or in a plugin that’s installed by default (and preferably on by default!).
I’m eager to see engineers from the Jaiku team at Google, and interested Python hackers, get into the OMB discussion on our mailing list. I, for one, look forward to having a connected network of diverse implementations — proprietary and Open Source — that can communicate through simple, clear open standards. Let’s take the steps to make that work.