Posted January 10, 2008 10:17 am by with 6 comments

Tweet about this on TwitterShare on LinkedInShare on Google+Share on FacebookBuffer this page

Google and Jaiku = gooku(two)Over at ars technica, there’s talk of Jaiku users fleeing to Twitter due to the lack of any innovation since being acquired by Google.

Google has allowed Jaiku to languish and is now suffering a backlash from frustrated users who are beginning to mass-migrate to Twitter, a competing microblogging service. Jaiku’s external feed servers, which are used by third-party Jaiku client applications, have been down frequently during the past week, often returning 504 gateway errors or nothing at all. During the brief stints when the feed servers are operational, they have been extremely slow and often out of sync with the actual content—typically lagging by between four and 13 hours.

I can attest to the poor performance of Jaiku. After the acquisition, I remembered that I had signed up for Jaiku many months before. I went back, logged in, and then added all of my social media feeds. Ten hours later, my Jaiku feed still hadn’t updated–I’ve not been back there since. I am however, very active on Twitter.

Jaiku founder Jyri Engestrom has tried to allay any fears that the service will follow in Dodgeball’s footsteps and join the “Google Sofa”–the place where acquisitions disappear behind, never to be found again.

Are you a Jaiku user? What’s been your experience since the Google acquisition?