Sorry for a slightly gaming subject line, but I've just worked out that the 'since_id' parameter is worthless in the mentions api call. It may also be the case in every other API call - but let me explain.
The only time that I can think that you need to use the since_id param is if you want to start looking at tweets from that point in time onwards. The API supports a count param, so technically I may only be interested in the first tweet since X id: If the tweet with the ID 1800200012 was posted 15 days ago (and I've had lot of mentions since) - I would expect to use the following call to get the mentions after that particular tweet: http://twitter.com/statuses/mentions.xml?since_id=1800200012&count=1 However, since the API call does all the mentions up to "now" - it gives me the my latest tweet. If there was a way to work backwards, i.e. in reverse order then it would solve this issue in one fell swoop. Possibly using: http://twitter.com/statuses/mentions.xml?since_id=1800200012&count=1&sort=desc This would be really useful for the personal timeline too, since I could track the first tweet when I got on holiday, and then follow each tweet since without having to depend on the search API (which is still limited to 3 weeks of data). What do you think? Should/could this be made in to feature? Cheers -- Remy Sharp
