The search API only has 7 days of history available, currently. Try the REST API for that user's updates. -- ivey
On Mon, Jun 29, 2009 at 3:50 AM, talklists <[email protected]> wrote: > > > http://search.twitter.com/search.json?page=4&max_id=2384515303&rpp=80&q=from%3Acometbus > > I have hit page 4 on that request. > Here is the JSON I am getting back: > { > "results": [], > "since_id": 0, > "max_id": 2384515303, > "previous_page": "?page=3&max_id=2384515303&rpp=80&q=from > %3Acometbus", > "refresh_url": "?since_id=2384515303&q=from%3Acometbus", > "results_per_page": 80, > "total": 240, > "completed_in": 0.273265, > "page": 4, > "query": "from%3Acometbus" > } > > This account has 1600 updates, so rpp(80)*4 = 320, which is much less > than 1600. The above is also a 404 page. I have read the docs which > tell me the below conflicting information. > > > http://apiwiki.twitter.com/Things-Every-Developer-Should-Know#6Therearepaginationlimits > Search API Limit Clients may request up to 1,500 statuses > via the page and rpp parameters for the search method. The > response to a request exceeding this limit will be a > status code of 200 and an empty result in the format > requested. This artificial limit is in place to ensure the > performance of the search system. We also restrict the > size of the search index by placing a date limit on the > updates we allow you to search. This limit is currently > around 1.5 weeks but is dynamic and subject to shrink as > the number of tweets per day continues to grow. > > I do not get a 200 response, I get a 404 response. I can not go back > as far as I would like to. Interestingly, the twitter website, as > well as tweetie client can go back much farther with no issue. > > Thanks. >
