A user named Kyrosan on IRC sent in this video of his cat answering an Adium sound (specifically, the contact-signed-off sound from the TokyoTrainStation set). Behold:
Thanks to Kyrosan for the video link, and to Robby (who is one of the people who help out on our Trac) for suggesting that I make a blog post out of it.
While writing this post, I couldn’t help but think of the story of another cat and Japanese train station.
As of 11:43 today (the 12th), MSN is now working for us in 1.3.2. Looks like the Libpurple team was right—it was a server-side problem, which Microsoft has now cleared up.
Thank you for your patience.
Starting at about 20:00 PST tonight (January 11), Microsoft’s servers have stopped accepting logins from clients that use version 15 of the protocol, including Adium 1.3.2. The Debug Window in debug and beta versions of Adium reveals that their server is failing to find a certificate that it needs when Libpurple attempts to retrieve your MSN Address Book.
In case you’re wondering, this also affects Pidgin, which means it’s definitely not an Adium problem.
There are two ways to connect:
We’re not sure whether this is a temporary server problem or a permanent change that will break P15-using Libpurple-based clients (including Adium 1.3.2) until a future Libpurple release. If it turns out to be the latter, we’ll almost certainly include that Libpurple update in our next 1.3.3 beta.
The question has come up a few times, so it might be helpful to explain. From your Google Talk account, send a message to +1XXXYYYZZZZ@sms.talk.google.com (US-only at the moment), or add it to your contact list. Voila!
This was pointed out in ticket #11488 in our Trac system.
