MahTweets – Customizable Twitter And Facebook Windows Desktop Client
MahTweets is the first ever desktop windows client that I have found to be totally customizable. It supports updates from Twitter, Facebook, RSS Feeds, Identi.ca, and 12seconds. They are all offered as plugins, you can add them one by one from Options. There are also upload plugins which allows users to upload photos to Flickr, Twitgoo, TwitPic, and Yfrog.
It is a standalone opensource client that doesn’t require Adobe Air. It has been developed on Windows Presentation Foundation and .NET Framework 3.5. It also makes use of some features of the upcoming .NET Framework 4.0.
From the Status Headline tab you can choose if you want to get notification alerts. You will also find options to enable translation to English(using Bing API) and enable TweetSaver screensaver.
In General tab you will find additional options, most of which have to do with appearance and performance. You can also choose the URL shortner from here.
Once you have configured all settings, the main interface will open up where you can add as many groups as you want and customize the appearance according to your needs.
For every tweet there is an option for DM, Retweet, Favorite, and Reply. On the right side you will find options to Add New group, Upload Photos, Settings, and Take Snapshot from Webcam. Below them there are options to Refresh and Clear all Streams.
Above every Group there are following options – Reverse order of column, Clear group, Edit group, and Delete group. On the status bar you will find the new updates for every stream(group) on the lower-right side you will find options to change the color.
In the screenshot below you can see how the Webcam Snapshot UI looks like. Notice the options on the left sidebar to update the display picture and also options to upload the image to web. These are given for Upload Photos feature as well which allows users to batch upload images.
The developers have listed the following important features on their page.
- Plugin Architecture
- Inline Pictures
- Tweet Splitting
- Auto-Expand Shortened URLs
- Filtering
- Multiple Uploading Services
With so many advanced features, it takes almost 86MB of system memory and can go as high as 100MB. Unless you don’t have enough memory, don’t even think about trying it. If the developers can decrease the memory footprint by half, there is a high chance that it will become my default client.
If you are have enough CPU horsepower and system memory then you can give it a try. Enjoy!
Hey, I'm one of the Devs from MahTweets. Thanks for the review. If you'd like to suggest ideas, I can't recommend strongly enough that you make use of our UserVoice page. That's the primary way we're tracking requests and issues. see http://mahtweets.uservoice.com/Regarding the request to halve the memory footprint: whilst reducing memory usage is something we'd like to see, our main goals to date have been ensuring we can provide a stable client that works well, has a good user interface, and providing good extensibility support. If I can see that memory isn't leaking, and that it's actually being used appropriately, then a few hundred MB isn't of terrible concern (to me, atleast). The UI framework we're using (WPF) actually sits at around 50MB to start with. See: http://stackoverflow.com/questions/1288477/why-… The cost of memory nowdays means that anything using less than a few hundred MB is really not a terribly big deal on a reasonably modern system.
Hey, I'm one of the Devs from MahTweets. Thanks for the review. If you'd like to suggest ideas, I can't recommend strongly enough that you make use of our UserVoice page. That's the primary way we're tracking requests and issues. see http://mahtweets.uservoice.com/Regarding the request to halve the memory footprint: whilst reducing memory usage is something we'd like to see, our main goals to date have been ensuring we can provide a stable client that works well, has a good user interface, and providing good extensibility support. If I can see that memory isn't leaking, and that it's actually being used appropriately, then a few hundred MB isn't of terrible concern (to me, atleast). The UI framework we're using (WPF) actually sits at around 50MB to start with. See: http://stackoverflow.com/questions/1288477/why-… The cost of memory nowdays means that anything using less than a few hundred MB is really not a terribly big deal on a reasonably modern system.
Hey, I'm one of the Devs from MahTweets. Thanks for the review. If you'd like to suggest ideas, I can't recommend strongly enough that you make use of our UserVoice page. That's the primary way we're tracking requests and issues. see http://mahtweets.uservoice.com/Regarding the request to halve the memory footprint: whilst reducing memory usage is something we'd like to see, our main goals to date have been ensuring we can provide a stable client that works well, has a good user interface, and providing good extensibility support. If I can see that memory isn't leaking, and that it's actually being used appropriately, then a few hundred MB isn't of terrible concern (to me, atleast). The UI framework we're using (WPF) actually sits at around 50MB to start with. See: http://stackoverflow.com/questions/1288477/why-… The cost of memory nowdays means that anything using less than a few hundred MB is really not a terribly big deal on a reasonably modern system.