You can use the since_id and since parameters to control which tweets to receive. Then strip out unwanted tweets on the client-side. Some timelines also offer a count parameter which allows you to specify the number of statuses you want returned.
There has been little chatter for a method that only returns ids, like the social graph API methods. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 4, 2009 at 2:50 AM, janole <s...@mobileways.de> wrote: > > Hi, > > not sure if the Twitter API people are reading in here, but let's give > it a try. > > I was wondering if you'd consider having an API call that's only > returning the last N status ids for your tweets/DM's/etc. a bit like > the extremely useful social graph calls friends/ids and followers/ids. > > I'm using a local tweet cache in Gravity (S60 Twitter client) and I > found it to be difficult to catch up with tweets/DM's that are deleted > by the user outside of the client's scope (web, other clients, etc.) > > Maybe there's an easy way to get around without "ids/tweets? > n=cachesizeN" or "ids/direct_messages?n=cachesizeN" like calls!? > > I'm trying to keep the traffic for the user low, so just fetching new > tweets with the "since_id" always set. This way, it's impossible to > synchronize the account of course. > > Let me know what you think of this or if I'm just too stupid to get > this done in another way. > > Cheers > Ole @ mobileways.de >
