Paging in method GET search/tweets


#1

method GET search/tweets has parameter “count” for records per page, but have no mechanism of paging.


#2

The concept of paging is being transitioned out of the API. You’ll need to use since_id and max_id to navigate between portions of a result set, as documented in [node:6213]. There’s still a little cleanup happening the metadata response of search results to better indicate this.


#3

So, all the search results are ordered by ID? and in this case I can use since_id, to navigate to second page, etc?


#4

Welcome to the National Anti Corruprtion Investigation Bureau’s (NACIB) Website. People think that Corruption simply means Bribery in general understanding, It is more than that. Corruption Means Injustice, misuse or disorder in morality, monetary, mental , Physical etc. Corruption Of any Kind are nuisances to the society. Corruption is the root cause of all the evils in the society. It hampers progress. It brings unhappiness. It Brings war. Corruption brings Crime in society.Across all India to hell identify, prevent, solve and reduce Corruption & Crime. We take urgent step and investigation all type of Corruption , Crime and other illegal work under Indian Govt. penal act.


#5

It would be really helpful if the documentation had at least ONE example in code of how to do this.
Twitter docs are not helpful.


#6

Pagication can be done using max_id parameter. To do this, pass the id of the most earliest tweet from loaded. Then the answer will come tweets whose id does not exceed passed max_id. However, there is a problem is that the response will include the already downloaded tweet whose id is equal max_id.

It would be great to solve this issue without conversion id_str to number and increment it, because javascript has problems with huge numbers