I've talked with the search team and there's a known condition where 10 of our servers are behind the others that can cause varying results across requests. We're aware of the issue, it is ticket and we are working on it.
On Wed, Nov 4, 2009 at 3:45 AM, Spode <[email protected]> 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=5402169538 > > 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=5402169538 > > And you get the expected 4 results. > > What's going on? > > Spode (journotwit.com) > -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
