Twitterlicious 2.1

Twitterlicious 2.1 After a two month absence of Twitterlicious updates, I’ve decided to change the way the UI work and get rid of the needless tabs for replies and direct messages. Now, everything is in one list, and any replies or direct messages are highlighted accordingly — blue for replies, and brown for direct messages.

Some people also reported issues with leaving Twitterlicious running, it sometimes stops updating and needs a restart. While I’ve not been able to reproduce this, I think I’ve found the problem and hopefully my solution will work.

If you have Twitterlicious 2.0, then it should automatically inform you of the update and how to upgrade, everyone else can get it at the usual place.

6 Comments

  1. Nick Carter December 18, 2007 at 10:46 pm

    Hey, I’m a recent devotee of Twitter, and I ride both Mac and Win platforms. On Mac I’ve settled on a combination of TwitterPost and moodBlast. (something I wish had a PC analog)

    On PC I had been simply working via IM but the convenience offered by a client couldn’t be resisted for long.

    ‘Licious offers many features I love. Conveniently compact view (I can even shrink to fit a single post and arrow through them perfectly. Great job!) keyboard shortcuts and nice simple interface. I love it.

    However, I’ve got a couple beefs that could prove its undoing. First, one thing Twitterific allows is to optionally switch to JSON vs XML. I’m not 100% that this provides significant benefit in this particular case but I know JSON overall provides a more compact format.

    More importantly, however… occasionally ‘Licious will hang on refreshing my tweet list, and will remain there for upwards of a minute. After finally calming down, (and if I uncheck the disable errors I get 3 error messages) it simply fails to retrieve any data after that. Hours go by and I assume no one has posted, but if I quit and restart Twitterlicious (or retrieve data any other way) I see I’ve missed posts.

    Something’s obviously going on.

    I apologize for the long comment and for not knowing where to seek support. If you’d direct me I’d gladly participate in any testing.

    -Nick Carter.

  2. weiran December 20, 2007 at 11:40 pm

    Hi Nick,

    Are you still having the problems with Twitterlicious 2.1? If so then drop me an e-mail, you can find details on the contact page.

    Also, there may be some legacy issues with people who’ve upgraded from 1.x, so that might be the issue too.

    Best, Weiran.

  3. Mark January 2, 2008 at 8:32 pm

    The installer that I download doesn’t seem to be Twitterlicious 2.1, but rather 2.0. I seemed to have downloaded 2.1 on my family’s computer, but when I go to download the update on my laptop it’s 2.0.

  4. weiran January 4, 2008 at 12:59 am

    Mark: if you’re upgrading from an old version you may need to uninstall it first, then install the new version. This was a bug in the installer for some old versions.

  5. Aditya Mukherjee March 14, 2008 at 12:23 pm

    Just a quick suggestion (great app btw!). It’ll be better if you provided an option to hide notifications for self-tweets. Currently, a balloon pops up even if the update one’s own tweet.

    Great work nonetheless!

  6. Dave March 31, 2008 at 9:30 pm

    I’m experiencing the same problem Nick described. I just signed up for twitter today and installed twitterlicious, so it is not an issue with installing over an old version. I have also reinstalled (well, “repaired”) .NET 2.0 in case of an issue with that, but twitterlicious is still failing to retrieve any messages other than at startup. All attempts to refresh messages after that produce a set of three

    System.Net.WebException: The operation has timed out

    errors, although the tracebacks for each are different.

    Any suggestions on resolving this would be appreciated.

One Trackback

  1. By Ejecutive » Twitterlicious 2.2 on September 2, 2008 at 10:42 pm

    [...] months ago, Twitterlicious 2.1 was released. Since then, I’ve just not had the time to fix some critical bugs that have been bugging me [...]

Add a Comment

Your email is never published nor shared. Required fields are marked *

*
*