Spread the Word | Create Account | My Account  
digsby

What Social Networks Do You Want?

The community run website at digsbies.org is holding a poll asking what social network protocols we should add next and we thought we would promote the poll a bit to get some insight:

http://digsbies.org/site/node/189

On another note, we have a new build right around the corner with a number of bug fixes including docking fixes and HTTP proxy fixes that are causing some people’s email accounts to not work properly. We also have something special planned for this build ;)

Comments

Build 27 – Making Your Monday a Little Brighter

We just pushed an update (Build 27, r14343 r14361) that introduces several critical bug fixes and optimizations. We are working on some very promising projects that will lower Digsby’s RAM usage and greatly improve user interface responsiveness. These are not quite ready to be pushed yet but we had a few important bug fixes that we wanted to push out to everyone. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Notable changes:

  • Proxy Improvements: You will now be able to get auto-updates and use web services such as Hotmail, Yahoo Mail, Facebook, etc. over proxies that block the CONNECT method (ie: SQUID). Those of you who have been affected by this will need to download and run the installer here.
  • CPU Spike Fix: We fixed a critical bug that was causing the CPU to climb to 100% (or 50% of you have a dual core processor). A few bugs that may cause this side effect still remain but we are working on them right now.
  • Twitter Fixes: Finally fixed the bug that caused Twitter popups to continuously appear for some users. We also optimized the Twitter update sequence so the 2-3 second freezes should no longer happen.

We are splitting our time between finishing up the RAM optimizations and knocking out bugs. We will have the optimizations wrapped up and pushed out as a single build very soon. We will also have HTTP login support for MSN soon so those of you who use it at work behind a restrictive proxy can log in. Thank you for all the feedback and enjoy the new build. If you experience any bugs please email us at bugs@digsby.com.

Update: The HTTP proxy fix resulted in a new bug that affected some SOCKS proxy users. We just a fix for this issue (5:45pm) and proxy support should be back to normal. Those who are affected by the bug may need to run the installer on our website since the bug affected the auto-update system. Sorry for the temporary inconvenience.

Comments

Digsby Nominated for About.com “IM Best Awards”

We are proud to announce that we have been nominated for the About.com 2008 IM Best Awards! We are nominated in five categories:

  • Best Instant Messenger Experience (Digsby)
  • Most Improved Instant Messenger (Digsby)
  • Best Third-Party IM (Digsby)
  • Best IM Feature (Social Networking and Email Integration)
  • IM Developers of the Year (dotSyntax, LLC)

Please show your support by voting for us: http://im.about.com/od/imreviews/a/IMBest.htm

The results will be announced on April 21st and winners in each category will be given featured placement for one year on http://im.about.com.

Comments

Build 26 – More Digsby, Less Bugs

We just pushed a small update (Build 26, r14192) that has a few bug fixes that we wanted to get out there before the weekend. For those of you who already updated to Build 25 it is also the first test of the new auto-update system. As always, you can read the entire list of changes on our Change Log. Most notably:

  • Fixed a few Twitter bugs including the “black infobox bug” and the “endless popups bug”
  • Fixed a bug that prevented some users from connecting to MSN Protocol
  • We also added log statements to help us find the rest of the cases where this may happen if any remain

Comments

Build 25 – If You Build It, They Will Come

We just pushed an update (Build 25, r14142 r14158) that introduces many new bug fixes and enhancements. It took us longer than usual to get this update out because we did not want to push any more updates until the new auto-update system was ready. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Notable changes:

  • New auto-update system: Digsby not launching due to partial updates should be a thing of the past. Since we are still using the old system to move to this build, a small portion of you will still need to run the installer if you get stuck.  If Digsby fails to start after this update, download and run the installer here.
  • Twitter Improvements: We have gotten a lot of feedback on the new Twitter implementation and much of that has been implemented. The new Twitter boasts improved performance, shorter default update timers, options to configure update timers, ability to manually update, and several other enhancements.
  • SNAC Error Fixed: This was caused by a protocol change on the ICQ servers and it is fixed in this build.

The goal for the next build is an important one. Every time we hear about Digsby’s RAM usage the response is, “we haven’t optimized yet; we wanted to get it out to the public to start getting feedback.” That time has come! We are going to focus on improving GUI responsiveness and lowering our memory footprint significantly for the next build! Right after that, the next few builds will focus on all the bugs you have reported. Thank you for all the feedback and enjoy the new build.

Update 1: We have gotten reports of a few bugs in the buddy list and with proxy support. We are fixing these right now and will have a new update out shortly. (9:30pm)
Update 2: The bugs we introduced are fixed and we pushed another build. There are a couple minor issues left that we will fix in the morning. There will probably be another build tomorrow with a few bug fixes and then we will focus on performance! (1:20am)

Comments

Auto-Updater: Test #2

Update: WOW – thank you all for testing the updater.  I think we got enough feedback that if you are just getting to this post there is no need to test it. We will do a code review tomorrow morning and push an update out.   It includes the new auto-updater and numerous bug fixes.  It also has new options for Twitter and much improved Twitter performance (the cache build up was slowing it down over time).

It seems that every time we push an update we get a few emails about Digsby completely not working afterwards. We have a new auto-update system that should solve this. Last week we asked some of you do test it out and we thank you for your help. We have made a few changes and would like to run one more test before pushing it out to everyone. The worst thing that can happen is it doesn’t work and you will need to download and run the installer from our website. No matter what happens, none of your preferences or account information will be lost. There are instructions below. Please post your results as a comment in this blog post.

  1. Download and run the installer located here:
  2. This will install a version of Digsby with the new auto-update system. When you launch Digsby it will check for updates. Since the version you just downloaded is not the same as the one everyone else has, it will actually revert back to the version you are currently running using the new auto update system.
  3. Please pay attention to what is happening during this process. It will download updates and restart Digsby. Once this is done, log in as you normally would and click Help > About Digsby. Make sure that you are back to version 13706.
  4. If Digsby just logs in and shows a version other than 13706 that means the entire update wasn’t downloaded. You should restart Digsby to let the update finish – this is not considered a failure.
  5. If anything went wrong, you can download the latest installer from our website and run it. There is no need to uninstall – that is the first thing that the installer does when you run it.
  6. Please post your results on this thread so we know if it is ready to be pushed to our entire user base. Make sure to include the following information: operating system, admin or not, UAC on or off (vista only), success or failure, other information about what happened.
  7. If the process fails at any point, please email update@digsby.com before reinstalling.

Sample Report 1 (success)
OS: Windows Vista
Account: Admin
UAC: On
Result: Worked

Sample Report 2 (fail then success)
OS: Windows XP
Account: Admin
Result: It downloaded some files but then logged right in without restarting. I checked the revision using Help > About but it was the wrong one. The I then exited and tried again. It downloaded a few more files, after which it restarted like it was suppose to. I then checked the revision it was was back to 13706.

Sample Report 3 (fail)
OS: Windows XP
Account: Non-Admin
Result: It downloaded files and then I got splash screen that said it was restarting along with an error. The error window had the title “XXXXX” and the error message was “XXXXX”. I am going email you right now for instructions on submitting more information about this error.

Comments

Testers Needed for New Auto-Updater

Update: Test #2 now taking place with a few changes – see the blog post with instructions here.

It’s a little past 3:30am and we just finished the new auto-updater! It seems that every time we push an update we get a few emails about Digsby completely not working afterwards and a few diagnostic logs with errors that we know don’t really exist. The reason for this is that a small portion of users get a partial update each time we push a new build. Additionally, if you are a non-admin user on Windows XP or Windows Vista the update would go into an endless loop because we had no way of knowing that the user doesn’t have write permission to the Digsby folder.

The new auto-update system is better in a few ways. First, it makes backups of all the old files and reverts to them all if the update fails at some point. It will just try again next time you restart Digsby. Second, for non-admin users it asks for elevated privileges, allowing an admin to put in their password so the update can take place. Third, while it is copying the new files from a temporary folder and restarting Digsby you now see a small splash screen so you know it is still busy.

Since the auto-updater is the most critical component (if we break it, then everyone would need to reinstall) we would like to have some of you test it before we push it to everyone. The worst thing that can happen is it doesn’t work and you will need to download and run the installer from our website. No matter what happens, none of your preferences or account information will be lost. There are instructions on our forum, which is also where we would like you to post your results:

http://forum.digsby.com/viewtopic.php?id=769

Comments

What IM Protocol Do You Want Next?

The community run website at digsbies.org is holding a poll asking what IM protocol we should have next and we thought we would promote the poll a bit to get some insight:

http://digsbies.org/site/node/137

On another note, we have a new build coming early next week with the Twitter enhancements you have been asking for, a more solid auto-update system, and numerous bug fixes.

Comments

LifeHacker Loves Digsby

LifeHacker is holding a poll to determine the best IM client and Digsby is in the race as one of the top five even though we publicly launched just two weeks ago.

The article gives us a great review saying, “Digsby has taken the world by storm… Digsby is converting new users left and right with their simple but appealing formula: IM + Email + Social Networking = Digsby”

Please support us by voting here: http://lifehacker.com/375391/five-best-instant-messengers

Comments

Show Your Support

I recently got an email from Brandon De Hoyos, the Guide to IM at About.com. They are hosting the “2008 IM Best Awards”, which will deliver top honors to the best instant messaging clients and their developers. About.com is accepting nominations for this honor in the following categories:

  • Best Instant Messenger Experience, measuring overall user experience;
  • Most Improved Instant Messenger, based on back-to-back client releases;
  • Best Mac Instant Messenger, based on overall user experience;
  • Best Third-Party IM
  • Best IM Feature
  • Best IM Developer(s) of the Year.

Winners in each category will be given featured Essentials placement for one year on http://im.about.com, in addition to all the bragging rights
among the IM community. These nominations must be e-mailed to im.guide@about.com for consideration.

Please show your support for Digsby by sending an email to Brandon at im.guide@about.com. Let me know why you love Digsby and which categories you want to nominate us for.

On another note, LifeHacker just published an article asking their readers, what is the best IM client? Check out the article and leave a comment here: http://lifehacker.com/374855/best-instant-messenger.

Thank you for your continued support as we make Digsby even better

Comments

Copyright © 2007-2017 dotSyntax, LLC.   All Rights Reserved