Hi Chad,
I believe this was caused by one of the two bugs I deployed fixes
for today [1]. Both of these were incorrectly returning 403 with the
message about old since_ids when it was not the case.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
[1] - http://apiwiki.twitter.com/REST-API-Changelog
On Jun 24, 2009, at 1:09 PM, Chad Etzel wrote:
On Wed, Jun 24, 2009 at 4:02 PM, Cameron
Kaiser<[email protected]> wrote:
I believe this error occurs when the search result would generate
more than
one page of results and a since argument (since or since_id) is
given.
Certainly something like that is bound to at some point, even at 100
reqs/page. I'm not fond of this implementation, mind you; I'd
prefer getting
the most recent page, plus maybe a warning in a separate field,
rather than
deepsixing the entire request.
No, I'm pretty sure that's not the case. I have several "high traffic"
searches going that regularly return 100 items, and I know there are
more. It never gives that response.
-Chad
