Hi Zac,
The response should also include a warning message that since_id
was removed. When you paginate we have to remove the since_id so
you'll need to keep track of the since_id and stop paginating when you
reach it.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jul 16, 2009, at 11:23 AM, Zac Witte wrote:
I'm paginating through a search query that was initially created with
a since_id parameter. I'm using the query suggested by next_page,
which includes a max_id and not a since_id, which I believe is the
correct usage. I'm still getting duplicate tweets. Is anyone else
experiencing this?
