Jaiku vs. Twitter, Round 2

One of our listeners of the Fresh Ubuntu podcast wrote in asking our opinions on Jaiku versus Twitter. Since I hadn’t really played with Jaiku for a while, I decided to give a shot at using Jaiku for a while, since I never gave it a lot of time a couple months ago, as I was already using Twitter and liking it. The first thing I decided to do was publish all of my Twitter notices into Jaiku. I did not do this a few months ago, because I was using Twitter for private (family and friends) stuff, and Pownce (and, by extension, Jaiku) for general notices.
I did have to put a little thought into this. Since I have several web feeds published into my Twitter history via Twitterfeed, as well as into Jaiku, I don’t want to have duplicates (i.e. Del.icio.us posts showing up twice) or make an endless loop, where Twitter would feed into Jaikus which would feed into Twitter into Jaiku ad infinitum. While it may be funny to read for a while, I’m sure it would get old very quickly, and don’t know that Jaiku and/or Twitterfeed have any provision for dealing with such a mess, other than to limit the number of posts they publish in any given amount of time.
After a little fiddling with my RSS feeds, I decided to make Jaiku my primary notification aggregator instead of Twitter, to give it a fair shot. I’m not considering Pownce for this again for now because logging in always requires a couple of steps – their homepage login never works for me and I have to enter my username and password again – and there is still no “Pownce mobile.” Even as lightweight as Pownce is, it’s a pain to navigate on my mobile phone.
Here’s how things break down now.
Reasons to Use Jaiku Primarily

  • Jaiku has built in RSS feed subscription. This means I would not need to use a third-party service (like Twitterfeed.com, (which requires an OpenID provider, which I use idproxy.net for (which uses my Yahoo! account))). Oh, the onion-like layers of indirection!
  • Jaiku has an application for my Nokia e61. Theoretically I’d get better performance out of it than loading a web page to post my updates.
  • Jaiku is owned by Google now, so it’s cooler.
  • Jaiku appears to publish its RSS feed more quickly than Twitter. I put a couple of Twitters in a few hours ago, and they still have not shown up in the RSS feed.
  • Twitter does seem to be down for maintenance a lot.
  • TwitterIM doesn’t always catch every post.

Reasons to Use Twitter Primarily

  • Most of my “social networking” is now done on Twitter, and a couple of the folks on my list only publish their notifications privately. I’m not sure if they will show up in an RSS feed out of Twitter. If they do, that’s bad, because I’m telling the public their private business. If they don’t, that’s bad, because I have to be on Twitter to see them, and if I’m using Jaiku as my primary interface for notices, I’m not likely to look at Twitter all that often.
  • I like the way Twitter works, usually, on my desktop and my mobile phone.
  • TwitterIM is offered by Twitter, whereas Jaiku requires use of Imified to work with AIM, Yahoo! and MSN. Interesting that they choose to work with Google, Jabber, and Livejournal, but not the most popular IM platform.
  • Jaiku is owned by Google, so it’s evil.
    Okay, I’m joking. A little. Seriously though, try and live a single day on the Internet without using anything Google. First off even if you don’t know it, you’re probably using Google search results somewhere if you’re doing any searching. Second, how many times do you interact with someone else who used Gmail to email you (yes, Google can read that email too), a PC running Google Toolbar (tracking your search patterns),or Google Desktop Search (keeping an index of all of your documents and email on their server). Gah, I gotta stop. This is a blog post in and of itself.

Follow my Twitters and Jaikus to see where I end up!
Update 2007-11-06: I’ve gone back to Twitter as my “main” and set Jaiku to subscribe to my Twitter RSS feed. We’ll see what happens.

Leave a Reply