As we mentioned last April, we are in the process of porting Jaiku over to Google App Engine. After the migration is complete, we will release the new open source Jaiku Engine project on Google Code under the Apache License. While Google will no longer actively develop the Jaiku codebase, the service itself will live on thanks to a dedicated and passionate volunteer team of Googlers. With the open source Jaiku Engine project, organizations, groups and individuals will be able to roll-their-own microblogging services and deploy them on Google App Engine. 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.
The rest of the Google Code announcement actual mentions the end of Dodgeball (also similar to Jaiku and Brightkite) plus the Mashup Editor (which I had never heard of). Technically, the Mashup Editor is also moving to the App Engine infrastructure.
I had heard rumours of the coming open source nature of Jaiku, but didn't think it would extend to Google itself essentially not further developing it. There has been talk of a tightening of focus, which is fine, but I think real time, Jaiku-like services (and really, Jaiku was first ... Twitter, Friendfeed, etc. came later) are going to become more important, not less.
The open sourcing of Jaiku should make one wonder about the recent funding for Identi.ca. I think what the Montreal Startup Fund guys are doing is fantastic, but don't know that I agree with putting money into open source projects before they've shown real traction.
That funding link points to a GigaOm post that also points to Twitter for Enterprise "clones" Yammer and Presently. I like both of those tools, and think they work great for internal / group communicatons. Stowe Boyd's write up of Presently is what made me go try it, plus we had a need for shared / private groups for Bootup Labs.
So, the open sourcing of Jaiku is one thing. The BIG thing is that this allows turn key public / private microblogging on a scalable infrastructure. No fail whale, you just get more resources via the underlying Google App Engine. And by turnkey, I mean anyone with a Google Apps for Domains account can follow a few steps to run their own instance, on their own domain.
Oh right, and by the BIG thing, I mean that this instantly catapults microblogging into a fully federated system: I set up jaiku.bootuplabs.com, which can federate with all the other Jaiku instances on Google App Engine. It's open source, so allowing one to map identities to Twitter, Identi.ca, or other systems is certainly possible as well. Or, as Presently does it, by pre-pending a special tag for posts you want to show up on other systems.
OK, I don't know if that last bit is true, I'm just hoping it is: will federation be turned on out of the box? Or an option? In any case, it's open source, so it would definitely be possible to add this feature.
One final question I have is where the centralized discussion of future features / development / etc. for Jaiku Engine?
I guess a code.google.com site will be going up, in the meantime there is the Get Satisfaction site. If we can, it might be useful to start a new "product" there called Jaiku Engine to differentiate it from jaiku.com (which theoretically will stay up).