[twitter-dev] Re: since_id too recent, poll less frequently

2009-04-16 Thread @Jalada
Dittoing Cameron here, Twitterfall isn't seeing it any more, though it was practically disabling us last night and I was getting concerned, because I slowed things down greatly but to no avail, and I thought I'd missed some update about it. The HTTP status code was 403 IIRC. Another +1 for

[twitter-dev] Re: since_id too recent, poll less frequently

2009-04-16 Thread Matt Sanford
Hi everyone, This error check has always existed in the search code, but most people never see it. This is a sanity check on the since_id parameter to prevent people using ones in the future. The problem yesterday was specifically that several back-ends fell behind. If you hit an up-to-

[twitter-dev] Re: since_id too recent, poll less frequently

2009-04-16 Thread @Jalada
I think it was the 'poll less frequently' that was throwing us all off. Glad to hear it was just a sanity check going...insane. -David On Apr 16, 4:01 pm, Matt Sanford m...@twitter.com wrote: Hi everyone,     This error check has always existed in the search code, but most   people never

[twitter-dev] Re: since_id too recent, poll less frequently

2009-04-15 Thread Nick Arnett
On Wed, Apr 15, 2009 at 5:26 PM, Doug Williams d...@twitter.com wrote: Cameron, Chad, and the Tweetfall duo pinged me this afternoon to let me know there is a new error cropping up from the search API. The error text is since_id too recent, poll less frequently. What HTTP status code is

[twitter-dev] Re: since_id too recent, poll less frequently

2009-04-15 Thread Cameron Kaiser
Cameron, Chad, and the Tweetfall duo pinged me this afternoon to let me know there is a new error cropping up from the search API. The error text is since_id too recent, poll less frequently. What HTTP status code is associated with this error? Any hint for how long to wait before