Byteblocks, Try using the page and rpp parameters in addition to
the since parameter:
# rpp: Optional. The number of tweets to return per page, up to a max
of 100.
* Example: http://search.twitter.com/search.atom?q=devorpp=15
# page: Optional. The page number (starting at 1) to return, up
Also, take a look at search.json. It will give you what to call for the
previous and next page of results. Or, it will give no previous or next
when you reach the last or first page. It also give the max_id and
since_id.
On Thu, Jun 11, 2009 at 9:16 AM, Rafe rafe.kem...@gmail.com wrote:
