We just pushed an update to alpha testers (Build 75, r25077 r25091 r25144) which includes a large number of bug fixes and enhancements.  As always, you can read the entire list of enhancements on our Change Log. Notable changes include:

• Fixed several of the most common crash causing bugs
• Fixed several issues with Twitter that caused Tweets to show in the wrong order on the timeline
• Blocked buddies now show a “blocked” icon where their status icon would normally appear on the buddy list

We are close to pushing the release to all users so if you experience any issues please use “Help > Send Bug Report” in the main menu to submit a diagnostic log or email us at bugs@digsby.com.

If you would like to become an alpha tester and get new releases before everyone else, download this file and place it in the main program folder. Keep in mind that as an alpha tester you may get a release with a few bugs every now and then.  We are looking for people who are proactive in reporting these issues so we can fix them before builds go out to all users.

Update 1 (11/16/2009 2:50pm): We just pushed an update fixing an issue that caused sent IMs to ICQ users to show as HTML.  The new build number is now 25091.

Update 2 (11/17/2009 1:25pm): One more small patch just got pushed out.  This one fixes the HTML in IMs issue for Pidgin buddies, fixes a bug that broke blocking in AIM, and updates the icon for MSN buddies that you block right away instead of when you click away from them.  The new build number is 25144.

We just pushed out a small patch to alpha testers (Build 74, r24927) fixing buddy list retrieval for Facebook Chat.  If you experience any issues please use “Help > Send Bug Report” in the main menu to submit a diagnostic log or email us at bugs@digsby.com.

We still get crash reports from a small portion of users.  These are issues we aren’t able to reproduce here so we need your help to hunt down the buggers causing the crashes so we can squash them!

• Does Digsby crash for you at least once a week?
  
• Do you have Visual Studio installed?

If the answer to both questions is a yes, then you can help!

We created a debug version of Digsby that does a lot more diagnostic stuff under the hood.   If you can get it to crash, the diagnostic log it generates will be extremely helpful in figuring out the cause.  If you would like to help, here are the instructions:

1. IMPORTANT: If you don’t have Visual Studio, the debug build won’t run.
2. Download this file and put it in the Digsby folder. If you already have a “tag.yaml” file, edit it to change the tag from “alpha” to “debug”
3. Restart Digsby so it can auto-update.
4. Log in and click Help > About to make sure you now have build r24922 r24945 r24959 r24978.
5. Next time Digsby crashes, if you get a dialog asking you to submit a crash report, submit one.
6. Instead of telling Windows to close the program, choose to debug it in Visual Studio (prior experience would help)
7. In the menu choose Debug > Save Dump As… and make a minidump of the current state of Digsby
8. Email that minidump to bugs@digsby.com

Thanks for your help!

Update 1 (11/5/2009 5:45pm EST): We pushed out a patch fixing a crash related to viewing chat history in the log viewer. New release number is r24945.

Update 2 (11/6/2009 6:45pm EST): Another day, another crash fixed. New release number is 24959.

Update 3 (11/10/2009 5:10pm EST): Keep those reports coming and we will be crash-free in no time!  New release with one more crash fix is 24978.

We just pushed an update to alpha testers (Build 72, r24777) which introduces more bug fixes building on the last alpha release.  As always, you can read the entire list of enhancements on our Change Log.

If you experience any issues please use “Help > Send Bug Report” in the main menu to submit a diagnostic log or email us at bugs@digsby.com.

If you would like to become an alpha tester and get new releases before everyone else, download this file and place it in the main program folder. Keep in mind that as an alpha tester you may get a release with a few bugs every now and then.  We are looking for people who are proactive in reporting these issues so we can fix them before builds go out to all users.

After a summer of non-stop feature releases, we are taking a little time to clean up the bugs, enhance performance, and tweak the usability of new features.  Thanks for all the great feedback you are providing!

We just pushed an update to alpha testers (Build 71, r24743) which introduces lots of fixes and interface tweaks.  As always, you can read the entire list of enhancements on our Change Log. Notable changes include:

• Fixed several of the most commonly reported crashes
• Fixed several significant memory leaks introduced in the last release
• Added diagnostic info to hunt down remaining crashes – please submit diagnostic logs if Digsby crashes

If you experience any issues please use “Help > Send Bug Report” in the main menu to submit a diagnostic log or email us at bugs@digsby.com.

If you would like to become an alpha tester and get new releases before everyone else, download this file and place it in the main program folder. Keep in mind that as an alpha tester you may get a release with a few bugs every now and then.  We are looking for people who are proactive in reporting these issues so we can fix them before builds go out to all users.

We just pushed an update to alpha testers (Build 69, r24489) which implements many of the usability enhancements and you have recommended over the past week along with a bunch of bug fixes. As always, you can read the entire list of enhancements on our Change Log. Notable changes include:

• Numerous Twitter Enhancements
• Possibly fixed a crash when returning from hibernate
• Possibly fixed a bug that caused AIM to disconnect a lot while sending IMs

We are close to pushing the release to all users so if you experience any issues please use “Help > Send Bug Report” in the main menu to submit a diagnostic log or email us at bugs@digsby.com.

If you would like to become an alpha tester and get new releases before everyone else, download this file and place it in the main program folder. Keep in mind that as an alpha tester you may get a release with a few bugs every now and then.  We are looking for people who are proactive in reporting these issues so we can fix them before builds go out to all users.

Update 1 (9/29/2009 10:45am EST): Today we’ve got some fixes for the Twitter issues from last night’s release. The new build number is r24497.

We just pushed an update to alpha testers (Build 68, r24416) which has a few new log statements to help us hunt down a crash that a few people have been reporting.

Update 1 (9/25/2009 1:55pm PST): Thanks to some of the changes from the previous alpha, we have a potential fix for the crash that we’re hunting down. There’s also a few usability enhancements for Twitter and some Hotmail bug fixes that you can read about on our changelog. The new build number is r24440.

We just pushed an update to alpha testers (Build 66, r24212 r24269) which has a new input box that will be capable of handling multi-formatting.

It currently only does per-message formatting and not per-character formatting but we are adding per-character support right now.  If you experience any issues please use “Help > Send Bug Report” in the main menu to submit a diagnostic log or email us at bugs@digsby.com.

Update 1 (9/18/2009 3:25pm EST): Rolled this back for now – not ready for prime time.  Thank you for the bug reports and crash reports.

Update 2 (9/19/2009 1:00pm EST): Fixed the reported issues and taking another stab at it.  The new release is r24269.  Please let us know if you run into any bugs with the new input box.

We just pushed an update to alpha testers (Build 65, r24127 r24143) which is primarily focused on ironing out bugs and usability issues from the last alpha. As always, you can read the entire list of enhancements on our Change Log. Notable changes include:

• Fixed a critical bug that caused social network accounts to disappear on login for some users
• You can now flip through entire Facebook photo albums in the newsfeed instead of just the pictures you see
• The Facebook newsfeed is now filtered to match the rules you set up on the Facebook website
• The research module now has its own section in preferences with info and options

We are close to pushing the release to all users so if you experience any issues please use “Help > Send Bug Report” in the main menu to submit a diagnostic log or email us at bugs@digsby.com.

If you would like to become an alpha tester and get new releases before everyone else, download this file and place it in the main program folder. Keep in mind that as an alpha tester you may get a release with a few bugs every now and then.  We are looking for people who are proactive in reporting these issues so we can fix them before builds go out to all users.

Update (9/17/2009 10:30am EST): We just pushed out a small patch fixing a bug with incoming Yahoo unicode IMs showing incorrectly and a bug that caused Facebook to get stuck in the Authenticating state.  This brings the release number to 24143.

We just pushed an update to alpha testers (Build 64, r23944 r24046) which introduces many new features and enhancements. As always, you can read the entire list of enhancements on our Change Log. Notable changes include:

• Facebook: A completely revamped Facebook Newsfeed that brings the full Facebook experience to Digsby.  Now you can post your status, comment on friend activity, “like” status updates, and even browse through photo albums.
• MySpaceIM: We added full support for MySpaceIM to our arsenal of protocols.
• Achievements: Share your achievements within Digsby with friends via Facebook Newsfeed.  There is more info about this feature on our FAQ.

This release is packed full of new features so we are expecting some new bugs to pop up. If you experience any issues please use “Help > Send Bug Report” in the main menu to submit a diagnostic log or email us at bugs@digsby.com.

If you would like to become an alpha tester and get new releases before everyone else, download this file and place it in the main program folder. Keep in mind that as an alpha tester you may get a release with a few bugs every now and then.  We are looking for people who are proactive in reporting these issues so we can fix them before builds go out to all users.

Update 1 (9/15/09 1:09pm EST): Small patch to help track down an issue with disappearing accounts.  If you notice that any of your accounts have gone missing, please submit a bug report immediately.