Alright, so turns out this is a known bug. http://code.google.com/p/twitter-api/issues/detail?id=1154 (thanks to cicero in the twitterapi chat for pointing that out)
The workaround seems to be grabbing ALL results and doing the since_id logic on my end. -Ryan On Apr 19, 4:12 pm, TweetByMail <rpill...@gmail.com> wrote: > I've been pulling my hair out over this issue for a couple days now. > As such, I've boiled down the problem to the basics. > > If I do a simple search:http://search.twitter.com/search?q=tweetbymail > > I get all the results just fine. > > I look at the second tweet down from the top, and take that tweet ID > number. Then I do another search using that as the since_id. (which > means there is definitely one tweet newer than that ID) > > http://search.twitter.com/search?q=tweetbymail&since_id=12474990991 > > No results! > > I've even lowered the since_id considerably and still returned > nothing. > > That happens most of the time, but the incredibly frustrating part is > that it does occasionally (rarely) work. It seems to happen if I'm > doing a lot of searches via the web interface in a short period of > time. > > I've spent hours/days on this with the same consistently inconsistent > results. (whether using the API or the web search) > > Am I missing something here? > > Thanks for your time, > > Ryan > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
