Was not including max_id in the Search API documentation an oversight?
Or is it not meant to be used with the Search API.

Providing a url like this : 
http://search.twitter.com/search.atom?q=kevin&max_id=8210191029,
returns what looks to be correct results, however, we can't afford to
not have this work in a couple months.

Any response would be appreciated.

Thanks,
Kevin

Reply via email to