I think a few people including myself have seen this. Best guess is that it's a caching issue on the twitter server side. Here are some other threads with similar issues:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e368ccc88f393885/a4f217e36b0d0657?#a4f217e36b0d0657 http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e6289b6439c1d26d/01bcafab31516f7a?lnk=gst&q=since_id#01bcafab31516f7a http://groups.google.com/group/twitter-development-talk/browse_thread/thread/ed72429eef055cb3/23cf597ef030ca62?lnk=gst&q=since_id#23cf597ef030ca62 On Nov 4, 3:45 am, Spode <sp...@justfdi.com> wrote: > Hi, > > I've been noticing some strange behaviour since last night - but > that's not to say it's not been going on longer. > > http://search.twitter.com/search.json?q=JournoTwit&rpp=100&since_id=5... > > Performing this search turns up 0 results when it should show 4. > > http://search.twitter.com/search.json?q=JournoTwit&rpp=100&since_id= > > Run it with no since_id and it works. Then straight away run the > original query... > > http://search.twitter.com/search.json?q=JournoTwit&rpp=100&since_id=5... > > And you get the expected 4 results. > > What's going on? > > Spode (journotwit.com)
