since_id help required


#1

When working with high traffic keywords and attempting to page using since_id can someone explain how the returned meta data works? I am given a refresh url and next results url but these seem to ignore my previous since_id parameter so I either end up indefinitely looping for new results or paging back into the dark depths of time with max_id.

If there has been (for example) 500 tweets since my last poll then when using since_id I would expect to be given five pages of results (with count 100) and would expect that the next_results would stop once it reaches my original since_id – however this does not seem to be the case, can someone clarify?


#2

any help on this one? I am now having to store the since id I started with and check it against the result set and halt paging then weed out the duplicates I get back…