It’s all coming together… I’ve seen that jaiku has IM support on the way in the unspecified future. I’m assuming jabber at least, but am hoping for AIM support as well.

Until then, because I want to be able to use jaiku on the go, I was gathering info on how to create a Blackberry app (have never done it, but is based on J2ME so shouldn’t be too terribly hard). I would have cobbled together just enough to make presence updates over JSON and view my overview RSS feed. But, as I was looking, I came across this project aiming to make a jaiku mobile app in 24hrs! So, I guess I can wait a few hours and see if this app will take care of my needs! The screenshots look cool. It’s neat that it’s being developed jaiku-style… with constant jaiku posts on the progress here.

This will be the final nail in twitter’s coffin, for my use. I had been continuing to use twitter over IM when I was out and about with my blackberry. With mobile access to jaiku, I don’t see any reason for me to use twitter anymore.

As I mentioned recently, though, twitter is servicing (or at least attempting to) many more requests per second than jaiku is… so maybe as jaiku grows the stability I’ve been enjoying will start to falter. The main reason I looked for a twitter alternative was all the outages and slowness. The reason I’ll stay with jaiku, even if it suffers under load, is commenting. Commenting rules.

Seriously, now that I am used to the enhanced jaiku features, twitter is starting to look a bit lame. They have a much larger user base, but if they don’t fix their stability issues it will start bleeding away. Web2.0 users are fickle…