Open qru23 opened 5 months ago
Instead of returning an empty value when no next results, it instead returns the previous cursor, making the last request repeat infinitely.
Unfortunately, that's how the Twitter Web API works.
An obvious short term solution is to check for a repeating cursor and stop iterating on that
Seems like a viable solutions, on it.
Currently, the way to check if the results have been exhausted is by checking if length of list
field of the response is zero or not. If it's zero, then results have been exhausted. But yeah, a no cursor might have been better.
There seems to be an issue with cursors repeating after pagination. This seems to be true for every tweet that has more than the limit set by the request.
Instead of returning an empty value when no next results, it instead returns the previous cursor, making the last request repeat infinitely.
An obvious short term solution is to check for a repeating cursor and stop iterating on that, but im not sure if there are any deeper issues involved.