In the US for a couple of weeks
May/090
I’m going to spend a couple of weeks on my old stomping grounds (the DC area) in the United States, visiting friends and attending a wedding. Today is the bachelor party. It’s more like a bachelor day really, as we’re going to go white water rafting in West Virginia! The weather seems alright so far and it rained a lot the last couple of days so there should be enough water to have some fun!
Unfortunately, as my camera is not waterproof, I won’t be taking any pictures during, which could have been a lot of fun.
First Adium / Twitter integration thoughts in 1.4 beta 1
May/092
It’s quite funny to see that, as I finally got some time to finish my first post on Twitter OS X desktop clients yesterday, a new one appeared the same day in the shape of Twitter support in Adium 1.4 beta 1. Well, to be fair, there already was support for Twitter in Adium but it wasn’t as widely available as a public beta. Here are some thoughts about Adium as a Twitter desktop client for OS X that I gathered as I used Adium exclusively for Twitter access yesterday.
First impression
First, there are some details on how this would work on Adium’s blog. Great read on the overall philosophy of the Twitter integration.
Not surprisingly, Adium tries to fit Twitter support into a chat metaphor. People you follow are automatically added to a new Twitter contact group, which is thanksfully collapsed by default! A new section called “Bookmarks” is also added (I’m actually not sure if that existed in previous versions of Adium and I just missed it) which contains a “Timeline (name of account)” bookmark for each Twitter account you set up. This actually didn’t work the first time I tried, which was quite disconcerting. According to Adium’s developpers, this is a bug that will be addressed with an upcoming second beta. At this point, restarting Adium should do the trick.
Timelines are actually group chats in which people you follow are participants of sorts. This is the core of Adium’s support for Twitter. Any time someone you follow posts a public tweet, it appears in the group chat window (modulo refresh period, of course). Noteworthy is the fact Adium lets you select a different appearance for group chat vs. regular, one-to-one chat, which is quite useful. An example of such a styled timeline can be seen below.

Direct messages are implemented as one-to-one chats as would be expected.
Limitations
The model of Twitter as group chat has limits though. First, there is no way, that I could find at least, to have persistent search results, i.e. an updated list of all the mentions of given terms. Just like timelines for your Twitter accounts are implemented as bookmarks in your contact list, I can envision persistent searches being implemented as a different kind of timeline.
Another issue is the fact that it’s not as easy to follow conversations as it is with dedicated clients. I assume the appearance extra that you use could help but, just as Adium adds links to the right of each post to operate on them (re-tweet, reply, favorite, permalink or, in the case of one of your posts, delete), a link to open a conversation in a separate window (similar to what Tweetie for Mac does) would be helpful. Obviously, it could become confusing with direct message conversations, since that’s how they are implemented as well…
The biggest issue at this point, though, is the fact that you only get tweets that were published while you are connected. It seems, because I just discovered this as I was writing and haven’t had time to explore more, that historical tweets that occurred while you were not connected are accessible from the so-called chat transcripts where it’s difficult to quickly see which tweets you’ve read and which you haven’t. Similarly, your timeline is reset each time you restart Adium, making it difficult to follow things as some tweets will be in your current timeline while others are hidden in logs…
Conclusion, for now at least?
Adium’s implementation of Twitter support is based around the group chat metaphor. It has potential but also some serious drawbacks at this time, ones that will make me go back to a dedicated Twitter client, at least for now. Of course, the software is still in beta and might still evolve, though I don’t know that it’s not already feature-frozen. A pretty cool feature, though one not directly related to Twitter support, is support for laconi.ca servers, as well as IRC support. What this means is that I could potentially use Adium for most of my communication needs (IM, Twitter and IRC) and that’s a big plus for me. IRC support is good enough that I can use Adium instead of Colloquy for my very simple IRC needs. All that’s missing to make Adium my one-stop communication hub is better Twitter support and Skype support (there’s an Adium extra to support Skype but I haven’t managed to make it work)… I suspect this is a big upside for lots of people and a big advantage over other desktop clients. I will therefore follow with interest how Twitter support in Adium evolves and might report back from time to time…
OS X desktop Twitter clients: Twitterrific and beyond!
May/094
I’ve had a Twitter account at the beginning of 2007 but it took me a while to really start using it. For one thing, I admit that I failed to see its potential then. Of course, it didn’t help that I didn’t know anyone with a Twitter account, thus not helping building interest… Any social application has to reach a critical mass, via positive feedback, where each new subscriber makes the whole network more valuable. I eventually got around to use it more intensively, as I started discovering usefulness to it and building a network. I do think though that the biggest impetus for me to use Twitter more was installing Twitteriffic on my computer.
You cannot underestimate the importance of a good interface to a service. When I started using Twitter, the only interface I knew of was the web version, which was failing quite a bit (state represented by the now infamous fail whale). Installing and subsequently using Twitterrific really helped me get into Twitter. I present here a short review of Twitterrific, what I like about it and what I look for in a Twitter desktop client.
Main window
Twitterrific is an application which only interface element is, when inactive, a menu bar icon (
), which allows to toggle visibility of the main application window and changes color when unread tweets are available. The application doesn’t even have a dock icon, which means that it won’t show up when you -tab between applications or doesn’t have a menu. Most, if not all, operations can be accessed via a keyboard shortcut. Of course, you can also interact with it via the mouse when the main window is shown, though as it doesn’t have menu bar, it takes some getting use to. A very useful feature is that it can react to a system-wide shortcut to display or hide the main window, which makes it easy to ready a new tweet or post something quickly.
The main window itself has a pretty simple layout though it can be a little alien at first as it is quite different from traditional OS X application windows. The timeline of received and sent tweets occupies most of the space. A simple control bar rests at the bottom, allowing you to access your Twitter home page, change Twitterrific settings (implemented as a modal sheet), refresh posts and post a new status. As you can see, it’s mostly targeted at reading as opposed to posting.
Posts are presented in reverse chronological order (most recent at the top), each displayed with its author’s avatar. Twitterrific remembers the last post you read and dim the ones you’ve seen already. Mentions are tinted so that you can distinguish them from regular posts. Same goes for direct messages. Note that there is no distinction made between replies and mentions, meaning that posts are tinted the same way regardless of whether they are direct replies or re-tweets. As long as your user name appears in it, a tweet will be tinted.
Interacting with a post
Selecting a tweet brings up three new icons, allowing further interaction. The first one is the gear menu, which provides lots of options, as shown on the screenshot to the left. A little surprising is the fact that this looks like a contextual menu, yet provides actions that are actually affecting the whole application. The second icon provides a quick way to reply to the selected tweet, while the third one sends you directly to the author’s web site, as defined in their profile.
Neat features
Twitterrific offers Growl support, the notification framework of choice on OS X. This goes very well with the overall application philosophy of staying out of your way, hidden until needed. You receive notifications when new tweets are available but you get informed in an non-intrusive way, allowing you to see them from the corner of your eye, while you keep doing whatever else you’re doing. To me, this was also a big plus to adopt Twitter, as it put me in control, kept in touch with the flux of things without having to check the details until I was ready to.
Last but not least, I find Twitterrific quite appealing to the eyes, despite the non-standard interface and it’s also very frugal resource-wise (both in terms of CPU time and RAM usage), which can be quite important when you have a bunch of applications running at the same time, all competing for your computer’s attention!
Limitations
To me, Twitterrific is terrific application for a Twitter beginner, and without which I probably wouldn’t have taken to Twitter as much as I have (or it might have taken me more time to do so). It’s also very well suited to what I would say is the majority of Twitter users (though it’s a wild guess on my part), i.e. people who mostly follow a limited number (think dozens, not hundreds) of people and post infrequently from a single account.
However, as I became more and more comfortable with Twitter, I found that Twitterrific, at least in its free instantiation, was missing some features that I grew quite fond of using my Twitter client of choice on the iPhone, Tweetie. I actually consider Tweetie for iPhone as the best client out there, all platforms considered, but that’s a story for some other time…
For one thing, Twitterrific (in its ad-supported version) doesn’t support multiple accounts, nor does it offer persistent search capability or ability to follow trends, all of which I became more and more dependent on to more efficiently use Twitter. I now commonly use 3 different accounts for different purposes and being able to use a single interface without jumping through hoops to post and read tweets from several accounts is a big plus.
Similarly, I rely on persistent search results to follow mentions of things that I am interested in (most often JBoss Portal), while I use trends an easy, real-time news engine (though one that’s obviously biased towards a wealthy, industrialized and rather frivolous society that can afford almost constant connectivity, but here also, this is a subject for a different time)… I also like/miss on the desktop the nearby functionality offered by most iPhone clients, which allow to filter tweets based on your location, which is an interesting way to see what’s going on locally and potentially find interesting new people to follow.
Moving forward
In essence, I have been searching for an OS X Twitter client that would replicate the functionnality offered by Tweetie on the iPhone. I don’t consider myself a Twitter power user but my usage pattern has moved beyond what Twitterrific comfortably handles. This is not a dig on Twitterrific. Like I said, it’s a terrific app that I would recommend in a heartbeat. I just outgrew the use for which it is optimized.
Requirements
What I want essentially from a (desktop) Twitter client is:
- multi-user account support
- ability to track trends
- ability to track search results
- Growl support
- streamlined interface (though what that means exactly is open to interpretation)
- ability to track where I stopped reading tweets
- native interface with low resource usage, i.e. not Air-based which I find quite the resource hog at this point
- free and opensource if possible (though I am not opposed to buying a client that I’d like, I bought Tweetie on the iPhone after all)
With these in mind, I’ve been / will be looking at several twitter clients to see which one sticks around. Probably more to come on this…
Tension
Apr/090
The weather is starting to warm up and it’s enticing me to take my bike for a ride. At the same time, each time I go out, I can see the surrounding mountains still very white (and I know that it has snowed a bit higher up) and it makes me want to grab my board and go ride some freshly covered canyon. Tension between wanting more winter and spring now!
My rogue finally made it to 80!
Mar/090
As I am waiting for my system updates to complete on my recently re-installed OS X, I figured I’d post something here while I wait…
I recently managed to reach level 80 with my rogue on World of Warcraft. It’s been quite fun running quests and accumulating experience again. It’s also very weird to find myself in a patchwork of different quality items (greens, *gasp*!), which I will now work on upgrading.
I haven’t had the opportunity to run many instances, what with a busy work schedule and the fact that I’m still playing on my old US-based server and I am now in France… So being able to run a 25-man raid last night with my crappy equipment was both eye opening and overwhelming. For one, I was quite lucky to even get on the raid, period. Despite letting a newb like me in, everything went so fast and smoothly that it made it painfully obvious how far back my play has dropped with my more-than-casual play of the last year or so… I will need quite a bit of work to get back into the rhythm of things: I still need to master my new build and its rotation, I’m clueless about the new buffs, and just overall rusty… I see a lot of 5-man instances in my future!
Updates all done, time for a restart and then, back to work!
Moutain biking diary: Néron tour attempt
Mar/092
The weather was pretty good today, not as good as yesterday but still nice. I decided to take my bike out and attempt an itinerary that I’d never tried before: a tour of the Néron mountain. The Néron is a mountain just north-west of Grenoble at the south tip of the Chartreuse massif:
Not long after moving to Grenoble, I bought a mountain bike itinerary book and I thought I’d follow their indications for this trip. Everything started rather well at my rather slow pace with a nice weather. Of course, it started getting colder as I climbed and ended up having to put my jacket on.
After about an hour of climbing, I was rather ready for the descent and that’s where the troubles started. Turned out the descent path was rather impracticable. To start with, it started a little too technique for my riding level but that’s not usually a problem: just unmount and pass the obstacles. However, as I was hiking down with my bike on my shoulder, it seemed like there were way too many tree trunks across the path. Now, you have to realize that this is/was a single track on a steep hillside with bushes on either side so there wasn’t much room to navigate or avoid any obstacles. Plus, many of the fallen trees were too high to be jumped over (I was able to slide my bike under several of these trunks).
After a while it appeared to me that maybe it wasn’t as random as it first appeared, especially considering the fact that I found white thread on the trail at several spots as well. Was it an attempt to prevent mountain bikers to ride this path? I don’t know but, after a while, it started to get tiring to have to carry the bike under/over fallen trees, trying to avoid brambles (tip: wearing shorts on an unknown trip involving single tracks: not a good idea!).
I finally arrived to a point where I saw hikers climbing up so I asked them how the path was further down, as they asked me how the path was looking further up. They confirmed that the trail quality didn’t improve significantly so I decided to cut my losses and started climbing back up. It was quite tiring to do so with the bike in tow but I was still not too far down, about only a 100 meters straight down, about 300-400 meters following the trail and it was better to have to climb now than get stuck further down the hill.
All in all, it was a little disappointing not to be able to complete the tour, especially since you always look forward to a single track descent after an hour climb! Of course, since I backtracked my path up, I enjoyed the descent on the road back but it cannot really compare to a single track. It was, however, good exercise and I got to see some really nice landscape.
I recorded my trip on pathtracks.com via PathTracker on my iPhone but my battery was getting low towards the end so the end of the trip is not really accurate. Still gives a good idea of what I did.
I will upload some pictures on my Flickr account as soon as I solve my current issue with my laptop kernel panicking as soon as I plug my camera in…
JBoss Portal 2.7.2 is released!
Mar/090
It’s been a couple of really busy weeks at work as we have been ironing out the last couple of issues that we wanted to solve before unleashing JBoss Portal 2.7.2 unto the world! ![]()
It’s finally done and 2.6.8 should follow suite soon. I can now re-gather my thoughts and energy towards 2.8 and beyond!
Read more about the release from our fearless leader on the official JBoss Portal blog.

