We just noticed a change in the AIM protocol – a new family of features has been added (family 0×25) that we have never seen before. It hasn’t been added to all the AIM servers yet so some of you will still be able to connect without a problem and some of you might get stuck in the Authenticating state. We are working on a fix right now and will push an update very shortly. We will update this post after it is pushed.

Edit:

We just pushed an update (Build 16, r12552) that fixes the AIM login problem along with several bug fixes and enhancements. You should be able to log in to AIM without any issues now. The list of changes can be found on our Change Log. So, what just happened? When we were developing the AIM protocol we designed it to break if we ever got something we never saw before. This raised a red flag so we could implement it. Since AOL adds features every now and then to the AIM protocol, this should have been turned off when we released digsby. Earlier today we saw a new set of capabilities on the AIM protocol (family 0×25) and that prevented us from logging in. The fix we just pushed does what should have been done at launch – ignore new capabilities instead of raising a red flag.