[Birdnest](http://nest.onedd.net) is a Twitter API proxy which filter out the unnecessary information off the Twitter response. This result better utilization of bandwidth for Twitter mobile client, primarily for [jibjib](http://sugree.com/project/jibjib).
What is birdnest?
Normally, Twitter does provide various methods to enable flexible access and interact with Twitter via its API. Many mobile clients are created in order to increase the tweet channel and help people tweet more frequent. However, Twitter API is not tailored for just mobile purpose. Return message of many methods become bloat and use too much bandwidth than it should be. For example, you may don’t want to know anything except than name of twitter-er who just replied to you at 30 seconds ago.
Size of the returned data directly effects the network cost, EDGE or GPRS. For normal use, air time cost is affordable. It’s vice versa for roaming. A specialized proxy which forward the request to the Twitter and throw away any unnecessary data before send it back to the client dramatically reduces the size of size. And that idea becomes Birdnest.
How to use birdnest?
Using birdnest is easy. Just change your Twitter API endpoint to one of our endpoints, in easy word change “http://twitter.com/” prefix to one of below choices, and that’s all. The API call will be forward to appropiate method on Twitter properly. And the response will be filter before hand it to you. Below are our available end points. Each end point reflects how to filter out the information.
No any filter. Just redirect the request
Filter out most of content from any error requests. The success response still return full data while the unsuccessful one will return ony HTTP error code
Filter out most data off the response except profile image.
Text only API. Throw every image url away. This filter return least size of data.
Birdnest also supports TwitPic. Send your picture to Birdnest and it will call Twitpic API for you. Save a load of Bandwith from nasty XML.
Found a bug, feature request?
If you found any bugs or want something implemented, don’t hesitate to tell us at [Birdnest project homepage](http://code.google.com/p/birdnest). Of course, any patches are welcome.