[twitter-dev] Search API: max_id and page parameters giving very weird results

2009-11-03 Thread TripleM
I've been trying to write a script to use the max_id parameter to loop through all 15 pages of results (with 100 results per page) without getting in troubles with grabbing the same tweet multiple times. Every time I do so, I find that not only are there a couple of duplicates on page 1 and 2,

[twitter-dev] Re: Search API: max_id and page parameters giving very weird results

2009-11-03 Thread TripleM
Except now that I look at it a day later, the results have completely changed, and seem to be in order. Why would the results change over time when the same max_id is set, and was valid at the time of the query? Are the ids of tweets not generated in ascending order? On Nov 3, 3:17 pm, TripleM

[twitter-dev] Re: Search API: max_id and page parameters giving very weird results

2009-11-03 Thread TripleM
. The first tweets on that page are much newer than the last ones on page 1. On Nov 3, 3:17 pm, TripleM stephenmerri...@gmail.com wrote: I've been trying to write a script to use the max_id parameter to loop through all 15 pages of results (with 100 results per page) without getting in troubles