TwiTsMAG.COM

rtweeter.com

Rtweeter is a Twitter and other Social Networking API that @stuartmanning is developing. The tools on Rtweeter only present a small proportion of the services that have been developed.

Rtweeter will provide you with tools that allow you to share longer tweets, shorten url’s and map :: And importantly you get user metrics. The services quietly went live on the 7th June.

Rtweeter is a free site for you to enjoy and make the most with. There will be a few more demo sites that will show how by using Maps and the other elements of Rtweeter can be reconfigured easily for different purposes [Demos expected by prior August 09]. Indeed, these will be just thought provoking mash-ups. These will include iPhone GPS support and other Geo-Location services that are already available on this site today.

Also, there are addition services that are being worked into a *new* desktop client whilst working on the API for the existing service as well as yet publically unveiled services.

Currently there is a FLEX client version of RTweeter [available to download from Rtweeter] and developers working on a comparable Silverlight 3 and WPF editions. One key feature of the original application was ’scheduling’ of messages, followed by ‘grouping’.

This is a one man venture, should you wish to help or have services to offer do get in contact  @stuartmanning

Rtweeter is already connected to 250+ sites using some of Rtweeter principles in how to market ’social links’ linking to Twitter, Facebook, Digg and other networks.

Desktop Client and how Rtweeter came to be

Rtweeter was created by @stuartmanning initially an experimental desktop client based on FLEX as an exploration to find out why Tweetdeck and other desktops took up such a large memory footprint on both the MAC and PC. This was launched on 17th March 2009 and was given a considerable amount of kind feedback from users who would request/bug and improve the client.

TweetDeck as an example runs about 400MB in memory :: Blu 128MB :: Rtweeter 48MB after an hour open :: Why is this? Well some twitter apps suffer from UI bloat – to many transitions and transparencies [especially] will take a high toll on memory and GPU resources :: However the most common fault is cloning and copying data objects in memory, poorly, to give extra services such as groups. Often these client make pure copies in memory when in fact they need only reference them once. Would say that it often poor Data Management in most cases [sorry if that offended anyone].

Whilst the Rtweeter desktop client is not at the exact stage Rtweeter would like it to be [forthcoming new app will bring in new services] it still is unique :: It most popular use is ‘Scheduling Tweets’ :: Users around the world in multiple languages use the desktop in many languages and it has often frustrated Rtweeter that I don’t have the time to do more for them. It has also be stated that the FLEX client may well go open source.

It was also important to bring in new and unique services, such as ‘Scheduled Tweets’ as a way not to bombard users with links that I was reading during the day :: It made sense to spread these out.