[twitter-dev] Re: Search API since_id doesn't work with filter:links
Yes I'm seeing this also, with this query: http://search.twitter.com/search.json?lang=enshow_user=truerpp=100since=2009-06-25until=2009-06-25q=Cloud On Jun 24, 7:57 am, Mojosaurus ish...@gmail.com wrote: Hi, My script polls Twitter APIs once every 15 seconds with a query likehttp://search.twitter.com/search.atom?q=video%20filter:linksrpp=100;... Starting 2009-06-23, this API returns http 403, with the following error message. hash errorsince date or since_id is too old/error /hash Did anything change in the last 24 hours? Is this a known issue, and when is it expected to get fixed? Any leads would be much appreciated. -- thanks, Ishwar.
[twitter-dev] Re: Search API since_id doesn't work with filter:links
Hmm, yes. I am seeing the same thing with the geocode: and source: modifiers. Is this a bug? -Chad On Wed, Jun 24, 2009 at 7:57 AM, Mojosaurusish...@gmail.com wrote: Hi, My script polls Twitter APIs once every 15 seconds with a query like http://search.twitter.com/search.atom?q=video%20filter:linksrpp=100since_id=2309008249 Starting 2009-06-23, this API returns http 403, with the following error message. hash errorsince date or since_id is too old/error /hash Did anything change in the last 24 hours? Is this a known issue, and when is it expected to get fixed? Any leads would be much appreciated. -- thanks, Ishwar.
[twitter-dev] Re: Search API since_id doesn't work with filter:links
We are seeing this as well. On Jun 24, 4:57 am, Mojosaurus ish...@gmail.com wrote: Hi, My script polls Twitter APIs once every 15 seconds with a query likehttp://search.twitter.com/search.atom?q=video%20filter:linksrpp=100;... Starting 2009-06-23, this API returns http 403, with the following error message. hash errorsince date or since_id is too old/error /hash Did anything change in the last 24 hours? Is this a known issue, and when is it expected to get fixed? Any leads would be much appreciated. -- thanks, Ishwar.
[twitter-dev] Re: Search API since_id doesn't work with filter:links
My script polls Twitter APIs once every 15 seconds with a query likehttp://search.twitter.com/search.atom?q=video%20filter:linksrpp=100;... Starting 2009-06-23, this API returns http 403, with the following error message. hash errorsince date or since_id is too old/error /hash Did anything change in the last 24 hours? Is this a known issue, and when is it expected to get fixed? Any leads would be much appreciated. We are seeing this as well. 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. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- FORTUNE: You can overcome any obstacle. Try a steeplechase.
[twitter-dev] Re: Search API since_id doesn't work with filter:links
On Wed, Jun 24, 2009 at 4:02 PM, Cameron Kaiserspec...@floodgap.com 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
