We just pushed an update (Build 18, r12783) that fixes many bugs. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Most notably:

• AIM realizes when the connection to the server dies
• Sending and receiving IMs in MSN is much more reliable now
• Digsby now works if your windows username has unicode in it
• Sent IMs show in the IM window right away instead of after the server confirms delivery - you will be notified if delivery fails
• AIM File transfers are more reliable now

If you still experience any of the bugs above please email us at bugs@digsby.com. Our focus for the next build includes:

• File transfer bugs (send some diagnostic logs of failures)
• Remaining CPU spiking bugs
• Revamping the auto-update system to ensure that a partial update (and a broken digsby) can never happen
• Start working on optimizing memory usage and plugging those leaks
• Perhaps a new feature?

PS: We ran out of ideas for catchy blog post titles when announcing new builds. Please leave a comment with some ideas!

Update:

We just found one of the bugs that caused CPU usage to spike to 100% and couldn’t wait to get it out there so we pushed another update (Build 19, r12811). We will do our best to solve the rest of the bugs related to this issue within the next 1-2 builds. Also, if you use Yahoo and have trouble staying connected please submit a diagnostic log. We want to try to knock this one out ASAP.

We’ve gotten reports of people being unable to connect to MSN Messenger. The official client yields the same results - their servers are down. But digsby lives on! We will keep you posted here.

Edit:

Everything seems to be back to normal and we are able to log in MSN Messenger from both the official client and digsby consistently.

We just pushed an update (Build 17, r12608) that fixes a few key bugs. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Most notably:

• Facebook no longer gets stuck in “Authenticating”
• URLs in IM windows get converted to links more reliably now
• Better (but not yet perfect) sending/receiving messages in MSN - you will still have bugs talking to buddies who go invisible or return from invisible
• Fix for entire buddy list showing as offline (and possibly partial buddy lists showing)
• Hebrew is no longer displayed as being backwards in the IM window
• IMAP accounts no longer show “Failed to Connect” when a single message is not understood - instead we don’t show the preview for that message

If you still experience any of the bugs above please email us at bugs@digsby.com. Focus for the next build includes:

• Any remaining connectivity or messaging issues that get reported
• File transfer bugs (send some diagnostic logs of failures)
• Partial buddy list showing up (on Jabber)
• Not being able to see your side of the conversation (submit diagnostic logs if it happens to you)

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.

We just pushed an update (Build 15, r12495) that fixes the most critical issues reported thus far. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Most notably:

• Fixed a bug that caused CPU to spike to 100%
• Fixes for sending and receiving IM’s on MSN Messenger (the last of them?)
• Multiple fixes for international versions of Hotmail and Yahoo Mail
• Facebook stuck in “Connecting…” bug is no more
• Attempted to fix Yahoo IM accounts for partner ISPs
• Fixes for Yahoo disconnecting for some users

If you still experience any of the bugs above please email us at bugs@digsby.com. We also added new print statements into the diagnostic logs that will help us fix the below issues. If you experience any of these, please use “Help” > “Submit Bug Report” to send us a diagnostic log and reference which one you are experiencing.

• Any remaining issues with connecting or authenticating on Facebook
• Any remaining email bugs connecting to an email account (especially IMAP/POP)
• Partial buddy list showing up (some buddies missing)
• Not being able to see your side of the conversation on Yahoo (unless this build fixed it, of course)

The primary focus for the next build will be to fix the above issues once we get some more logs. We will also put a lot of emphasis on fixing some of the smaller bugs now that major connectivity issues are out of the way. Enjoy!

We just pushed an update (Build 14, r12317)! This build has a few bug fixes but it is mostly changes in the diagnostic log system that will help us hunt down the causes of recently reported bugs. Most notably:

• Fixed all known bugs with sending/receiving messages on MSN
• Fixed the proxy bug which was causing some users to see a “we are upgrading” message. There are a few remaining proxy bugs that are being resolved right now and will be pushed in the next update

Biggest priorities for the next build are:

• There is still a bug with CPU usage spiking and we will have that resolved shortly. If digsby tells you that it is performing poorly and asks whether or not you wish to send a diagnostic log we would appreciate it if you could click yes - it will help us resolve the problem more quickly.
• We added log statements to fix the bug where Facebook gets stuck “Connecting…” - if you can reproduce this please submit a diagnostic log using “Help” > “Submit Bug Report”
• Fixes for email errors that people are reporting - mostly due to improperly parsed messages or international versions of email accounts (ie: @yahoo.es)

As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. We will launch the community forum later today so you can discuss digsby, suggest features, and help each other out. Along with that, we will release bug reporting guidelines that will help us deal with issues more efficiently. Enjoy the new build and if you have any issues send an email to bugs@digsby.com.

We couldn’t let this one wait until morning! We pushed a new update with a few major connectivity fixes:

• Fixed a bug that caused digsby to freeze when connecting to Yahoo Messenger
• Fixed a bug that caused digsby to get stuck in “Loading Skin…”
• Fixed a bug related to firewalls that don’t allow non-http traffic over port 80

We just pushed an update that fixes the most critical issues reported thus far. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Most notably:

• Fixed the “Connection Lost” bug when connecting to digsby
• Fixed IMs not sending sometimes on MSN Messenger
• Unicode support in auto-update system for those with international versions of Windows or with Windows usernames that have unicode.

Our biggest priorities for the next release are:

• Performance optimization, remaining connectivity issues, and most requested usability optimizations
• Fixing the Facebook “Connecting…” bug - we added more log statements that will help us fix this. If you experience this please submit a diagnostic log using “Help” > “Send Bug Report”

We are working on a fix for the “Failed to Connect” bug with the new proxy server code. We will push a fix as soon as it is ready.

Our update from yesterday caused connection issues for some people, so today we pushed another update. To get the update, just sign out of digsby (or exit the program) and sign back in. Hopefully this will be the end of everyone’s connection issues! If you’re still having trouble please e-mail us at bugs@digsby.com or use the “Submit Bug Report” feature in the “Help” menu of digsby.

As always, keep the feedback and bug reports coming!

-Mike