404 with Twitter Search API and since_id

[jan]

Hi folks,

could someone help me by telling me why

http://search.twitter.com/search.json?q=from%3Amitchfanning&since_id=1066081654

yields a 404 while

http://search.twitter.com/search.json?q=from%3Alayzdaisy&since_id=1097277226

works like a charm? Is the id too old in the first case?


Thank you very much for your help. Best regards,

Jan

[Matt Sanford]

Hi Jan,

    The search system requires the since_id to be a status ID in the search database. That requirement allows us to lookup the date on the status in question and perform some crucial optimizations. In the case of 1066081654 that status is not in the search database so it throws a 404. In this case, the user "mitchfanning" was flagged by our support team about three months ago and search updates stopped.

Thanks;

  — Matt Sanford / @mzsanford

[jan]

thank you very much for the explanation, matt!

On Jan 6, 10:36 pm, Matt Sanford <m...@twitter.com> wrote:
> Hi Jan,
>
>      The search system requires the since_id to be a status ID in the  
> search database. That requirement allows us to lookup the date on the  
> status in question and perform some crucial optimizations. In the case  
> of 1066081654 that status is not in the search database so it throws a  
> 404. In this case, the user "mitchfanning" was flagged by our support  
> team about three months ago and search updates stopped.
>
> Thanks;
>    — Matt Sanford / @mzsanford
>
> On Jan 6, 2009, at 11:51 AM, jan wrote:
>
>
>
> > Hi folks,
>
> > could someone help me by telling me why
>

> >http://search.twitter.com/search.json?q=from%3Amitchfanning&since_id=...
>
> > yields a 404 while
>
> >http://search.twitter.com/search.json?q=from%3Alayzdaisy&since_id=109...