I guess two posts on lifestreaming clients isn’t enough?.
Yesterday MacHeist started offering pre public beta access to Tweetie 2 for Mac. That caught my eye because Syrinx, my primary Twitter client has been a little slow at keeping up with Twitter features. I didn’t really want to get the MacHeist bundle (don’t want to hassle with packages that I don’t want) just to get the private beta, but I mentioned on Twitter that I was thinking about it. Several folks suggested that I try Echofon. I gave it a whirl, found some things that I like and other that I didn’t. I started keeping notes about Syrinx vs Echofon, and now it’s turned into a blog post.
My usage style / requirements
I follow a bunch of people, including many people who live in Europe who tweet while I am asleep. I need a client that can remember unread tweets from overnight. I’ve found very few clients that are able to do this. My reading style tends to be bursty as well, so I want the client to do a good job of keeping track of what I’ve read and what I have not. These two requirements are what has kept me on Syrinx – it can hold days worth of tweets without a problem. Syrinx’s bookmark also gives me definite way of marking what has been read and what has not, and puts control of that mark directly in my hands.
The other major requirement is that I spend some time (probably too much) on airplanes, without net access. I want a client (mostly on my iPhone) that can go back in fill in the gaps left by being in the air. Tweetie 2 for the iPhone can do this, but the experience of switch back and forth between reading the stream on desktop Syrinx and iPhone Tweetie 2 is annoying.
A minor requirement is to be able to monitor a number of Twitter searches at once – that means opening a window for each search, something that Syrinx also does.
Now, let’s have a look at how Syrinx and Echofon stack up for me.
The obvious things that I like about Syrinx are that it can hold as many tweets as I want, as well as the bookmark. I’ve also grown accustomed to the way that it displays time in absolute format, something which Tweetie 2 / iPhone also does. One other nicety in Syrinx is that it can display real names in addition to Twitter handles, because sometimes handles and people are hard to match up. When you have tons of tweets lying around in the? client, sometimes you want to go back to one, and Syrinx obliges with the ability to search all the tweets that it currently has in memory.
So what are the problems with Syrinx? It’s been occasionally unstable, but not in a show stopping fashion. It doesn’t have good support for lists, but I still haven’t made much use of lists. Syrinx does great on opening windows for searches, but it doesn’t remember what searches you have open, so you have to keep track of that yourself. Probably the biggest drawback of Syrinx is that its development is going slowly because its author has a day job.
When I compare Echofon and Syrinx, I realize that a lot of the things that I prefer in Echofon are niceties. I like that it can open browser links in the background. I like the way that the drawer is used for dealing with Twitter users and profiles and for displaying conversations. I just wish it could display more than one conversation at once – but that’s hard in the drawer model. The ability to colorize tweets matching keywords makes it easier to pick out tweets on high priority topics. As a photographer, I appreciate the ability to display pictures without going all the way to the browser. I do wish there was a way to get some kind of preview of those pictures right in the tweet stream. Echofon does this clever thing where it combines “rapid-fire” tweets from the same person. This seems to work really well, and the visual cue is definitely helpful.
Looking at the tweet authoring side, I love the “retweet with comment” option. One reason that I stopped commenting on retweets was that it was annoying to do it. No more. Echofon can tab complete Twitter id’s when @replying or direct messaging. I still wish for a direct message “rolodex” – there are some people who have hard to remember Twitter id’s. bit.ly is my preferred URL shortener because of the analytics, but you have to be logged in to bit.ly in order for that to work well. Fortunately Echofon is able to log into bit.ly accounts so that your analytics work.
In theory, I like the idea of an Echofon ecosystem that syncs the desktop and mobile clients. I haven’t tried this yet because I have iPhone Twitter client fatigue, and because as much as I like Echofon, there are some issues that make it hard for me to switch over.
The first of these issues is that Echofon won’t hold all of the tweets that happen overnight. It looks like Echofon will hold about 5 hours of tweets before it starts to drop them on the floor. There go some of those European tweets.
The next big issue is that marking read/unread doesn’t work for me. If I am scrolling up through my home tweets and I hit the top, everything gets marked read. It’s easy to do that by accident. Switching to the @, DM, or search tabs also marks my home tweets as all read, and that doesn’t work for me at all.
Compared to those two issues, everything else is just nits, but here goes, just to be complete. Echofon doesn’t display absolute time or real names. Also, Echofon doesn’t let you search your home tweets.
Wild and crazy wishes
Certain URL shortening services (su.pr and ow.ly come to mind) wrap the page in a header bar, which is annoying. I’d love if my client would route through those services so that the URL that I got in the browser was the actual content.
Sometimes there are links that are retweeted a bunch. I would love it if a client could compress all those retweets into a single entry which showed how many / which people I follow retweeted a link, along with an indication of whether or not I had already “read” an earlier retweeter (which would mean I had already read the link).
I guess I’ll have to do another version of this post when Tweetie 2 for Mac finally ships. Or maybe it’s still early enough for some of these ideas to make the cut.