I've also noticed issues with since_id on multiple API calls. The docs state for since_id...
"If the limit of Tweets has occured since the since_id, the since_id will be forced to the oldest ID available. " I've found this to not be true and many methods return the newest Tweets. Rhys On Jul 29, 6:04 am, Matt Harris <thematthar...@twitter.com> wrote: > Hey Gary, > > I think you mean the search API but i'm not sure. > > If you can provide an example of the request you are making to the API, the > response (as search changes quickly) and the ID you then use for since_id > i'll take a look and check what's happening. > > Best, > Matt > > > > On Wed, Jul 28, 2010 at 4:45 AM, Gary <gbre...@gmail.com> wrote: > > Hi, > > > I've got a question about since_id and if it actually works. > > > The API states - > > > since_id: returns tweets with status ids greater than the given id. > > > So when I get a list of 100 twitter messages, I store the maximum id > > in that group, which I get from the id property after stripping out > > "tag:search.twitter.com,2005:" and use that id for my since_id the > > next time I run the query. The problem is I've noticed I get back id's > > that I've already seen in previous requests when using since_id. It is > > fine for me I just ignore them I just thought I'd bring it to the > > attention of you guys, unless I've misinterpreted this functionality. > > > Thanks, > > > Gary > > -- > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris
