Digsby Blog http://blog.digsby.com The Official Blog of the Digsby Instant Messaging Client Thu, 19 Jun 2008 15:22:24 +0000 http://wordpress.org/?v=2.5.1 en AIM Servers are Down http://blog.digsby.com/archives/45 http://blog.digsby.com/archives/45#comments Tue, 17 Jun 2008 15:05:01 +0000 Steve http://blog.digsby.com/?p=45 The AIM login servers are down. This is system wide and you will not be able to log in with AIM 5.9, AIM in Gmail, Digsby, or other third party IM clients. AIM 6+ connects to a different set of servers and connectivity seems to be more reliable if you need a temporary solution. We will post an update here once service is restored.

Update: It looks like the AIM servers are back online.

Update 2: AIM servers are down again as of June 19th, 11:00am EST

Update 3: It looks like AIM servers are back online as of June 19th, 11:20am EST

]]> http://blog.digsby.com/archives/45/feed Vote for Digsby! http://blog.digsby.com/archives/44 http://blog.digsby.com/archives/44#comments Mon, 16 Jun 2008 14:32:51 +0000 Steve http://blog.digsby.com/?p=44 ReadWriteWeb is holding a poll to see what the best IM clients are. This is a follow-up to an article they wrote about IM interoperability, in which they boldly stated:

Digsby is poised to take a serious amount from the market share of the standard clients because of its interoperability not only with IM clients, but also because of the integrated social networks and even email. It makes me wonder if maybe Digsby is poised to be the “Firefox” of instant messaging if the dominating players aren’t careful.

Please show your support by voting for us: ReadWriteWeb Poll

On another note, it has been 2.5 weeks since our last release, which is uncharacteristic of us. As the bug reports began to die off, we have bunkered down to fully optimize our codebase. The next release will bring a few significant improvements including:

  • Major reduction in RAM (memory) usage
  • Fixes for most of the memory leaks
  • A much more responsive user interface
  • Ability to connect to IM networks even if your firewall/proxy restricts that port
]]> http://blog.digsby.com/archives/44/feed Twitter Issues http://blog.digsby.com/archives/43 http://blog.digsby.com/archives/43#comments Thu, 29 May 2008 22:34:53 +0000 Steve http://blog.digsby.com/archives/43 Twitter has been experiencing server-side issues with their system so they temporarily lowered the limit of requests applications can make from 70/hour to 30/hour. You can adjust your request levels by double clicking on your Twitter account in preferences and choosing “Advanced” - otherwise you will hit rate limits and not receive updates.

They have also created a website where you can monitor their status and they will announce when the limit is brought back to 70/hour on there: http://status.twitter.com.

]]> http://blog.digsby.com/archives/43/feed Build 31 - MSN Conversation Fixes http://blog.digsby.com/archives/42 http://blog.digsby.com/archives/42#comments Tue, 27 May 2008 20:46:26 +0000 Steve http://blog.digsby.com/archives/42 We just pushed an update (Build 31, r15078 r15142) that fixes the last of the known bugs with MSN conversations along with a few other bug fixes and enhancements. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Thank you for all the feedback and enjoy the new build. As always, if you have any issues please email bugs@digsby.com.

Update: We pushed a small fix for Facebook Chat.  A change in the protocol resulted in Digsby disconnecting/reconnecting every 10 minutes.  This will no longer happen.

]]> http://blog.digsby.com/archives/42/feed Build 30 - Woot! http://blog.digsby.com/archives/41 http://blog.digsby.com/archives/41#comments Wed, 21 May 2008 14:45:49 +0000 Steve http://blog.digsby.com/archives/41 We just pushed an update (Build 30, r15001 r15021 r15034) that introduces several bug fixes and enhancements, including a few significant usability improvements. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Notable changes:

  • Account Connectivity: Email and social network accounts now retry three times with two second pauses between retries before telling you that it failed to connect. Also, the popups which tell you that it failed to connect are not sticky anymore so you they will go away without you having to click close
  • Facebook Chat: Added typing notifications to Facebook Chat, fixed a bug that caused some incoming messages to not show, and fixed a bug that prevented some international users from logging in
  • New Authorization Dialog: It now shows you what account the add request is for and lets you “Authorize/Add” in addition to just “Authorize” so you can also add the person to your buddy list

Thank you for all the feedback and enjoy the new build. As always, if you have any issues please email bugs@digsby.com. We are running out of catchy blog post titles for the releases. Leave a comment with some ideas.

Update 1: We had a very productive day today so we wanted to push another update. The new release number for Build 30 is r15021. We fixed two bugs that prevented auto-update from working, a bug that prevented the InfoBox from showing, a bug in the new authorization dialog, a bug that caused Jabber accounts to disconnect on roster changes, and a bug that caused the CPU to spin to 100%. Connection lost error popups will now only show once until the connection is reestablished so they are less annoying. Also, auto-updates will not take place on Windows 2000 since the auto-updater does not work on Win2k.

Update 2: We just pushed a tiny update for a bug we introduced that caused Digsby to have trouble reconnecting to our servers after returning from hibernate on laptops.

]]> http://blog.digsby.com/archives/41/feed MSN Servers are Down http://blog.digsby.com/archives/40 http://blog.digsby.com/archives/40#comments Fri, 16 May 2008 23:06:10 +0000 Steve http://blog.digsby.com/archives/40 The MSN buddy list servers are down so you will not be able to log in MSN Messenger. You may be able to log in with the official client because it caches your buddy list on the hard drive. We will let you know when we see the servers come back online.

Update: It looks like they fixed the issue pretty quickly. MSN should be able to connect now.

]]> http://blog.digsby.com/archives/40/feed Build 29 - Dude, You’re Getting a Digsby! http://blog.digsby.com/archives/39 http://blog.digsby.com/archives/39#comments Tue, 13 May 2008 17:21:00 +0000 Steve http://blog.digsby.com/archives/39 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 bugs@digsby.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.

]]> http://blog.digsby.com/archives/39/feed Build 28 - Facebook Chat In Digsby! http://blog.digsby.com/archives/37 http://blog.digsby.com/archives/37#comments Thu, 01 May 2008 19:54:19 +0000 Steve http://blog.digsby.com/?p=37 You asked for it, you got it! Build 28 (r14688) introduces Facebook Chat support! This is our first implementation so you can expect many improvements over the coming weeks. Please let us know if you run into any bugs so we can fix those too. There are several other important updates in this release. As always, you can read the entire list of new features, bug fixes, and enhancements on our Change Log. Notably:

  • Facebook Chat: You can now chat with all your Facebook friends right from Digsby! This initial release includes all the basics - messaging, buddy icons, status, and status messages. We will add the ability to sync your IM status with your Facebook status and the ability to move Facebook buddies into other groups shortly! Facebook Chat is completely separate from the social network support we currently provide for Facebook so you need to add your Facebook account to the IM accounts list.
  • Yahoo Mail: This build introduces an improved implementation of Yahoo Mail. Those who had trouble accessing their mail should now be able to get to it. If you use the New Yahoo Mail instead of Yahoo Mail Classic, the “Inbox”, “Compose”, and “Open” links will take you to the right interface. Lastly, international accounts now show the correct email address such as @yahoo.co.uk or @yahoo.es instead of @yahoo.com. Please let us know if the new implementation has any bugs.
  • Proxy Support: All known bugs with proxy support are now resolved! We also have a suite of proxy tests now to simulate various environments before pushing new builds so it doesn’t break in the future. If you are behind a proxy you may not be able to get this auto-update but that will be a thing of the past after you download and run the latest installer from the website.

We are working diligently on finishing up the RAM optimizations, fixing the CPU spikes, and improving GUI responsiveness. We have a few highly reported bugs that we will tackle for the next build along with any that get reported about the new features. Thank you for all the feedback and enjoy the new build. If you experience any bugs please email us at bugs@digsby.com and send requests to features@digsby.com.

]]> http://blog.digsby.com/archives/37/feed What Social Networks Do You Want? http://blog.digsby.com/archives/36 http://blog.digsby.com/archives/36#comments Mon, 28 Apr 2008 18:49:33 +0000 Steve http://blog.digsby.com/?p=36 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 ;)

]]> http://blog.digsby.com/archives/36/feed Build 27 - Making Your Monday a Little Brighter http://blog.digsby.com/archives/35 http://blog.digsby.com/archives/35#comments Mon, 21 Apr 2008 15:51:46 +0000 Steve http://blog.digsby.com/?p=35 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.

]]> http://blog.digsby.com/archives/35/feed