Search API : Pagination is out of order

[Hrishi]

Hello all,

I collecting location based tweets.
I am using max_id and page parameters for pagination.
The ids of the tweets returned seem to be out of order.

For example :

Go to:
http://search.twitter.com/search.json?geocode=40.70771%2C-73.948974%2C15km&rpp=100&q=&page=1

Then go to page 2 using next_page value

The ids of last results from page 1 are much lower than top results of
page 2.
In other words page 1 returns older results than page 2.
Is this a bug or am I doing it wrong?

Thanks

[twitterdoug]

Looking into this.

On Mar 10, 1:36 am, Hrishi <bakshi.hrishik...@gmail.com> wrote:
> Hello all,
>
> I collecting location based tweets.
> I am using max_id and page parameters for pagination.
> The ids of the tweets returned seem to be out of order.
>
> For example :
>

> Go to:http://search.twitter.com/search.json?geocode=40.70771%2C-73.948974%2...