Hi there,
This is a server side problem we're working on. Some of the
servers are lagging and we're trying to fix it as fast as we can.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On May 12, 2009, at 12:41 PM, jgillman wrote:
I am using the following search query in my app but 9/10 times it
returns results that are 40+ minutes old. Every once and a while it
will return results up to the second. I am only making the request
once a minute (via a cron job) and double checking that the next tweet
I'm about to display has a time-stamp greater than the one I'm about
to post. But this throws the whole thing out of whack when my first
request pulls tweets from 20-30 seconds ago and then the next one
pulls requests 20-30 MINTUES ago.
I'm absolutely beside myself as to why this is happening as I get the
same results (sometimes old, sometimes new) when I do the request in
my browser and just look at the returned xml.
Here is the query I'm using:
http://search.twitter.com/search.atom?ors=relax+swim+summer+vacation+concert+drink+refreshinglang=encount=45
I've also tried using rpp=45 and since_id=last_ID_pulled but neither
have produced results that are any more consistent.
-Joel
