@Alan: Surely a search on “download tweetdeck version 0.38.2 for chrome” will soon turn up what you need? That’s really all I did to find OS X versions. And that said, isn’t Adobe AIR a cross-platform thing anyway?

@Alan: Ah, Chrome is a foreign land for me. We’ll see if anyone adds some info here, I guess…

@Wade: Indeed. That’s the entire point of AIR, right? But the post ended up like this because it wasn’t planned and constructed. It simply evolved. On an evening when my main focus was very much elsewhere. I’ll tell the story because it explains why all sorts of things online — and in the rest of life, for that matter — are the way they are.

On the evening of 8 January, I’d just done three or four days of solid work with little sleep, including one almost-all-nighter. Some of that had been incredibly frustrating because my MacBook Pro was getting a bit crashy. A bit too crashy, across multiple applications. And the AIR version of TweetDeck was being one of the crashiest.

I made the decision: nuke it from orbit and re-install everything.

Since this is my only computer and I was at the Bunjaree Cottages and a long way from assistance, I started compiling an archive of installers and serial numbers for all my software. I threw them into a directory with “OS X” in the name. When it came to TweetDeck, I simply retrieved a known-good version from my Time Machine backup. I called the file TweetDeck_OSX.zip because everything else was being labelled like that.

I figured this could be useful for other people, so I wrote this post, tweeted a link, and went back to work. Very little thought went into it. According to the revision history, the entire process took five minutes.

Twenty minutes later someone who saw my tweet emailed me “the Windows version”. So I added it. Amount of thought involved: two-fifths of fuck all. And so it went. And there you have it.

What amuses me is that the crisp formatting of my website gives the overall impression of order. What this post should really look like is pure chaos. A dining table still strewn with dirty crockery and an empty wine bottle from a rushed dinner, scribbled notes and me — unshaven, tired and very stressed.

What also amuses me is that you’re the first person to mention this, more than two months later.

I’ll fix the post is due course, and I thank you. But I’m actually concentrating on other things today. And so it goes. And there you have it.

@Ginevra: I can confirm that the problem exists, at least on OS X, but we won’t be able to fix this. The URL re-writing is going wrong between the Twitter API and TweetDeck — and of course we don’t have access to that layer. Twitter is no longer supporting this version of TweetDeck, nor do we access to the source code, so we can’t fix it ourselves. And I can’t suggest a workaround because, again, we have no access to the software layers in question.

I don’t know that this appeared in the change from TweetDeck 0.38.1 to 0.38.2, though. My gut feeling is that it appeared when Twitter introduced their t.co URL shortener into the loop.

So why don’t you just roll back to version 0.38.1? If you don’t have your own backups — and why not? — just copy the application file from your husband’s Mac. That’ll soon confirm whether it’s that version number difference or not.