UK Web Focus (Brian Kelly)

Innovation and best practices for the Web

Do You Want The Good News Or The Bad News About Jaiku?

Posted by Brian Kelly on 28 Jan 2009

A service announces that the software is to be made available under an open source licence. That’s good news, isn’t it?

A company announces that one of its is to be withdrawn. That’s bad news, isn’t it?

But what if a service makes both announcements in the same press release. How should we react to the news?  That’s the dilemma which uses of the Jaiku micro-blogging service are faced with following Google’s announcement: “Changes for Jaiku and Farewell to Dodgeball and Mashup Editor“. Vic Gundotra, Vice President, Engineering gave a positive spin to this announcement “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“. He then went on to add that “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“.

Some commenters focussed on the move to an open source licence (e.g. “Jaiku is going open source on Google App Engine“) whilst other headlines were more negative (“Google kills Jaiku“). For me, however, the interesting aspect of this news is how it should help to move the discussion on beyond simplistic cliches and perceptions.

A couple of articles struck me as particularly interesting.  An article published in The Enquisitr entitled “Google Massacre: Google Closes Jaiku, Dodgeball, Notebook, Catalog Search; Google Video Downgraded” felt that “The cut to Jaiku puts what was once a promising platform out of its misery. Since acquiring Jaiku, Google has all but ignored the service, culminating in a weekend long and seemingly unnoticed downtime in August.

Meanwhile a Techcrunch article entitled “Jaiku Founder: ‘We’re Not Dying, We’re Morphing’” has generated a lively discussion on Google’s motivations for this announcement. I needed to read the statement that “But few people seem to care that handing out the code to the open source community and starting the ‘Jaiku Engine’ project is actually great news for companies, groups and individuals who were looking to roll their own, decentralized microsharing / lifestreaming applications, initiatives we’ve seen pop up here and there already” in order to make sense of it.

But the comment that “If the code that Google is releasing only makes it possible for you to run “Jaiku Engine” only on Google’s App Engine, then it is not open enough. I have the feeling that this will be the case.” is intriguing.  Are Google buying software such as Jaiku in order to ensure they will run on their platform engine before making the source code available to others in the belief that the big money is to be made in providing the platform and not the application.

Now isn’t this the approach which has proved so profitable for Microsoft over the past 20 years? And, if so, isn’t Jaiku just a pawn in a much bigger game?  But on the other hand if you’re simply a user of such services, maybe you don’t care about issues such as ownership and open source. And, after all, it’s the users who ultimately determine whether a service will be used or note, not the developers.

7 Responses to “Do You Want The Good News Or The Bad News About Jaiku?”

  1. Well, if it is going open source, then I guess people will be free to port it to other platform providers too (especially as Google App Engine is based on Python, which other platform providers support).

    So Google’s pitch to be the platform provider of choice for an open-source Jaiku will be based upon ease of use, speed, cost and other factors, rather than code or licence based ‘lock in’.

  2. Overall it’s bad news. Google is the new place startups go to die.

    There are already several Jaiku-alikes which are open source. Releasing another which is tied to a vendor’s infrastructure (in particular a niche infrastructre which requires a different approach to databases to every other application or infrastructure in the world) is not that useful, even though it could, with time, be ported (in fact I suspect this would need to be a fork). The people I know have suggested that it’s having to port to that exact infrastructure which led to its death.

  3. Oh, sorry, “morphing”.

  4. […] Do You Want The Good News Or The Bad News About Jaiku? […]

  5. Eddie Byrne said

    My use of Jaiku took a bit of a dive when the Facebook ‘Jaiku’ app suddenly disappeared (its developer no longer wished to maintain it). I used it primarily to update my FB ‘presence’, keeping Twitter for another use. Why I wonder have the Jaiku developers not taken up the mantle, surely they see the value of its use in conjunction with other social networks like FB? Shame, I like Jaiku as is (was?).

  6. Eddie – because after Jaiku was bought they had two tasks:

    * stop feature development and port it to App Engine
    * anything else that’s not Jaiku

  7. […] is the new place startups go to die.” – Phil Wilson #Jaiku #Google_graveyard « előző | Africa Feed — 2009. 02. 16. […]

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: