We've started seeing this too. If we specify a since_id, then periodic refetches will frequently return "no new tweets" (but sometimes they will return new ones). If we simply drop the since_id, then all new tweets are fetched.
Some new server optimization thing gone wrong? Thanks! On Oct 20, 10:06 pm, Christopher Warren <christopher.war...@gmail.com> wrote: > We have an app that runssearchesregularly, and recently stopped > receiving newtweets. After investigating we found a search > combination that seems to break the search API. Instead of getting a > response withnotweets, an .atom request errors and a .json request > 404s. > > http://search.twitter.com/search.json?q=from:silent_tester02&since_id...http://search.twitter.com/search.atom?q=from:silent_tester02&since_id... > > Changing the query to not use from:username works as expect, but I've > put several usernames in and they all respond the same way. I haven't > managed to narrow down the cause of the problem much further than > that, but we're handling it in our code by rescuing any failedsearchesand > appending since: with the date of the most recent tweet > to the q. > > Any thoughts on what might be causing this would be appreciated.
