Adium

Archive for the ‘MSN’ Category

Microsoft will be dropping MSN for Skype

Friday, January 18th, 2013

It has been reported that Microsoft will be dropping MSN Messenger in favor of Skype.[1]

From what we’ve been able to gather, it should be possible to use MSN in Adium until March 2014.[2] As of this moment, it is not legally possible for us to integrate Skype support (more information: [3], [4]).

Historically, Microsoft has not necessarily encouraged third-party clients connecting to MSN, but they have been tolerated. Not long ago, Microsoft added an XMPP interface to connect to MSN, however it was lacking features and it will be shut down in October. While it’s possible that they could someday add one for Skype, they haven’t provided any indication of doing so.

We know that many of you rely on MSN and we understand that this news is frustrating. It’s frustrating for us as well because, as of right now, we aren’t left with any options. We’ll have to see how this all transpires over the next year. If we find a solution, you can be sure that we’ll let you know.

Adium 1.4.3

Sunday, September 4th, 2011

Adium 1.4.3 is now available. For the full list of changes and all the gory details see the release notes.

Here are a few of the more prominent changes:

Facebook Chat
Facebook will now connect via the officially-sanctioned mechanism (Facebook page on the API).  You no longer have to provide Adium with your username and password; when you first log in, you will be prompted to authenticate via a facebook.com window. Existing Facebook Chat accounts are upgraded automatically.

MSN
We reverted Adium 1.4.2′s change to libpurple’s MNP16 support from MSNP15. This should fix direct file transfers, user icons, and receiving custom emoticons, while disabling multiple points of presence (MPOP). We determined that this was the better trade-off based on user feedback.

Other important changes
We also fixed Twitter connectivity for many, a common crash, and activated the overlay scrollers for Lion.

Support and development
As always, if you find a bug or have a question, please refer to the Help page.

…And if you’d like to help us out in any way, feel free to find out how you can contribute.

 

Onward to 1.5!

Adium 1.4.2

Monday, June 13th, 2011

Adium 1.4.2 is now available. It includes, among other improvements, fixes for the following major problems:

  • a frequent MSN crash
  • an MSN issue adding contacts
  • an MSN connection problem involving the error “Signed in from another location”
  • ICQ losing connection without showing
  • Hang when opening a chat window to a contact with a malformed log

Message style improvements
We have also addressed the complaints about the focus indication we added to the bundled message styles for the 1.4 release. They are now only shown in group chats and the indicators for Mockie have been redone.

For more details on the changes in Adium 1.4.2, you can read the release notes.

Libpurple tradeoff
However, you will find that on MSN the following features do not work in Adium 1.4.2:

  • direct file transfers
  • user icons
  • receiving custom emoticons

We had to decide whether we wanted to update libpurple, the library which provides network-level connectivity for most services in Adium, to fix the major three MSN issues mentioned at the top and we decided that is was worth it despite these feature regressions it brings.

*Clarification: These features are currently broken in 1.4.2. They were not removed. We didn’t decide to throw them out. It’s simply that they are broken in the included version of libpurple. We had to make a decision between updating to fix a large number of other bugs while knowing these 3 would be broken, or leaving them untouched and leaving several services COMPLETELY broken for a number of our users. We chose to do the most good for the most people. It was one or the other.*

Where’s Facebook migration?
We originally intended to offer a migration path from the old to the new implementation of Facebook Chat in Adium 1.4.2. However, the implementation isn’t ready yet and with the many major issues already fixed in 1.4.2 we decided to push Facebook migration to 1.4.3. So for now, if you have problems with Facebook, you’ll have to manually switch as outlined here: http://trac.adium.im/wiki/FacebookChat.

Support and development
As always, if you find a bug or have a question, refer to the Help page.

And if you’d like to help us out in any way, feel free to find out how you can contribute.

What’s next?

  • Twitter connection issues (for Adium 1.4.3; see the Help page for details)
  • Facebook migration (for Adium 1.4.3)

MSN now working again

Monday, January 12th, 2009

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.

MSN rejecting Adium 1.3.2 connections

Monday, January 12th, 2009

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.

Apple resolves MSN connectivity problems in 10.5.3 update

Thursday, June 5th, 2008

Those of you who’ve used MSN via Adium on Leopard may have observed Adium taking a very long time to connect, or not connecting at all. A lot of you sent us bug reports about this.

The problem wasn’t a bug in Adium, or even in Libpurple. In Mac OS X 10.5.0, Apple changed the way it looks up hostnames, such as the one for the MSN server. They changed it to use a “SRV” request instead of an “A” request.

Unfortunately, some ISPs’ domain-name servers only knew how to handle “A” requests, and would ignore the “SRV” requests. That’s what was causing the problem: broken domain-name servers.

In Mac OS X 10.5.3, Apple changed its lookup method back to the earlier behavior. So, for those of you who had this problem, MSN should now connect again, without workarounds such as using OpenDNS.

Microsoft censors your messages

Saturday, August 4th, 2007

From time to time, a user emails our feedback address reporting that he tried to send a message and got this error:

Could not send; a connection error occurred.

And I never had an answer for those users, because it’s quite an empty error message (“a connection error”? What kind of connection error?) and I never heard anything from the other developers about it. So I always wondered what caused that error message.

Now I’ve found out.

A user on the IRC channel mentioned that he had received that error message. Specifically, he started out asking whether there was a way to “fix sending of URLs through MSN”. I asked for more info, and he revealed that he got the same error message when attempting to send a URL that had a .info domain. I tried a couple such URLs myself, with David‘s help, and confirmed his report—even http://growl.info/ doesn’t work.

The reason MSN gives for this censorship is that it’s to protect users from exploits that use certain URLs. The problem with this reason is that any URL could be an exploit URL; filtering by keyword just isn’t enough, because the attackers can always invent new filenames. The correct solution is simply to fix the exploits.

There’s nothing we can do about this because it’s done on the server. This also means that all clients are affected, not just Adium.

We now have a page on our wiki titled MSN Censorship which contains a (probably incomplete) list of strings that are known to get a message blocked. If you include one of these strings in your message, the message will not arrive and you’ll get the “connection error occurred” error message in your chat window.

If you’d like to not have these problems anymore, we suggest switching to Google Talk or Jabber. If you’re using Gmail/Google Mail, you already have a GTalk account; you need only set it up in Adium and get all your friends to switch. (And yes, as a couple of comments point out, you also have the option of using OTR encryption—but that only works if the contact you’re talking to is also capable of OTR. If they’re running Adium or Pidgin, then they are, but not if they’re using some other client, such as the official MSN client.)

(Sources include Arve Bersvendsen’s blog post and Joost de Valk’s blog post. Joost de Valk is the user I mentioned above. If you use Digg, please digg his post.)