Whoa! Who turned up the heat? Servers are running a bit hot right now, please try again in a couple minutes, Jaiku mumbled and passed away. I thought to give Jaiku a third chance now that it got a new infrastructure, a new license agreement and invites but things turned out to be cold, if you know what i mean.
Jaiku recently moved to App Engine, Google’s own flavor of The Cloud. Apparently the new servers don’t seem to help a lot or at least they run hot when someone tries to import a new video feed to his profile, which is what i tried to do before i face the sparrow bird of fail.
Speaking of fail and downtime, twitter comes in mind but over the past months, the Twitter team managed to phenomenally reduce downtime, go through the last Apple Keynote pretty much stable and now touting its horn with Elections 2008 and a new home page face lift.
I can think of 3 reasons for Jaiku bird of fail error message.
- Micro-blogging is getting so popular and mainstream that even App Engine is unable to handle the load
- Python code needs some tweaking to get all that love App Engine has to offer
- The force doesn’t want me to use Jaiku anymore
I don’t want to see Jaiku becoming the new twitter in downtime. It’s bad for the micro-blogging ecosystem and it’s unfair for content publishing, plus it produces poor and less relevant results in Google search. That, i do not like.