We just pushed an update (Build 29, r14878 r14905 r14938) which is focused on general bug fixes, enhancements, and a few important MSN fixes. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Notable changes include:
- Major overhaul for MSN Conversations to fix bugs that caused messages to not be delivered sometimes
- Fixed a bug that caused the CPU to spike to 100% if an MSN file transfer fails
- Added a backup auto-update system in case Amazon S3 has issues again like it did last time
- Added support for unicode and extended ascii passwords
We are getting very excited about the RAM and performance optimizations we are working on. These should be ready within a few weeks. We are also working on the last of the CPU spins and HTTP login for MSN Messenger for the upcoming builds. As always, thank you for all the feedback and enjoy the new build. If you experience any bugs please email us at email@example.com.
Update 1: If Digsby crashes on auto-update, we found the cause for this… it is a bug with Windows XP SP2 and Microsoft has a fix for it so if you run windows update and get all the hotfixes it will not happen (http://support.microsoft.com/kb/921337). We are working on a fix that will avoid this windows bug regardless of whether you have the hotfix or not and we will push an update shortly! You will need to reinstall after the fix is pushed but it will not happen again.
Update 2: We just pushed a fix (now r14905) for the crash on auto-update. It was a bug introduced into Windows in SP2 and fixed via an optional hotfix or by installing SP3. We now completely avoid the issue so if you download and run the latest installer it will not happen next time you update whether you have the Windows fix or not. Additionally, we fixed a bug that caused Digsby to not dock on startup if it was docked when you exited and a bug that made it impossible to close the IM window in certain cases after sending an offline message to someone.
Update 3: We just pushed a fix for the Facebook Chat protocol change in r14938. Thanks for letting us know it stopped working. Also, if a Twitter update fails, it will retry 3 times before telling you that it failed. Their servers seem flaky at times so we shouldn’t annoy you with a popup without retrying under the hood at first.