You are here: Home » Stuff » Jaiku Closed for the Weekend Pending Upgrade

Jaiku Closed for the Weekend Pending Upgrade

August 24, 2008

If Twitter were down for one, two, or even three consecutive days, would you crack? For the heaviest, most avid of users, I think yes. But when the microblogging service Jaiku, acquired some 9-10 months ago by Google, told its users to take a weekend breather the past couple of days, few in the blog world raised the issue. Zach Epstein at the Boy Genius Report jumped on it, made a quick joke. But other than he, there seems to be little in the way of OMGs, WTFs, and various other three- and four-letter caps-sized exclamations.

However, having looked at responses by Jaiku Invites and ZDNet’s Googling Google blogger Garett Rogers, it appears that the service isn’t quite “down for the count,” so to speak. Instead, there’s morsel-sized evidence Jaiku is taking this short hiatus to enact a real shift in performance to give Jaiku that extra umph on the Google App Engine people have anticipated for a number of weeks now.

Indeed, the company did mention earlier this month that it was moving its wares over to the App Engine, and it delivered a few words on the Jaikido Blog about the effort to port the thing as it was underway. But this new memo asking everyone - users, visitors, woops-wrong-turners - to take a breather may well bring about that gleeful and long-awaited phew-ahhh troubled members have been waiting for. Otherwise, it’s just, you know, a few days of downtime. Which even on the Twitter barometer circa Q1 and Q2 2008, would connote doom, gloom, and nasty scarring to boot.

---
Related Articles at Mashable! - The Social Networking Blog:

Jaiku Releases New Microblogging Tool for Nokia S60
Jaiku on Your iPhone
A Day Without Jaiku…
WidSets to Launch Jaiku Widget
Jaiku Hosting Markku’s Channel for Eurovision 2007
Will Google Use Jaiku to Collect Data on You?
Jaiku’s New Mobile App to be Unveiled at Supernova

Leave a Comment

Spam Protection by WP-SpamFree

Previous post:

Next post: