{"id":744,"date":"2009-02-24T16:15:02","date_gmt":"2009-02-24T08:15:02","guid":{"rendered":"http:\/\/www.whoisandrewwee.com\/?p=744"},"modified":"2009-02-25T22:29:30","modified_gmt":"2009-02-25T14:29:30","slug":"tweetdeck-users-read-this","status":"publish","type":"post","link":"http:\/\/whoisandrewwee.com\/social-networking\/tweetdeck-users-read-this\/","title":{"rendered":"TweetDeck Users Read This…"},"content":{"rendered":"

I’ve discovered a major problem that plagues Tweetdeck users who use the free Twitter client to access and post microblogging updates. TweetDeck is bugged by a fairly major issue which will require a solution pretty soon.<\/p>\n

Background: I’m an active Twitter user and have been using what I would consider the best Twitter client, TweetDeck, for a couple of months.<\/p>\n

Sure it’s had some weird idiosyncrasies like having to shut it down so I could run more bandwidth-intensive applications or MMPOGs on my system, but on the whole, it’s been a pleasant experience (read my earlier review<\/a>)<\/p>\n

I may or may not be the typical Tweetdeck user – here’re my usage habits:<\/p>\n