Looks like we've got some bugs here, as neither of these behaviors/limitations are intentional. Please file issues at http://code.google.com/p/twitter-api/issues/entry and we'll get them taken care of.
On Sat, Oct 18, 2008 at 3:46 AM, Phil Gyford <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm trying to archive all my twitters to a local database. I'm using > user_timeline but have hit a couple of problems. > > First, if I set the 'count' parameter to the maximum of 200 and ask > for 'page' 2, then it doesn't fetch back tweets 201-400, but instead > fetches tweets 21-220. So 'count' does not affect the number of tweets > on a 'page'. So if you set the count to 200 and request several > incrementally numbered pages, then you're soon only getting 20 new > tweets each time, plus 180 you've had before. There doesn't seem much > point in being able to set the count higher than 20 unless you're only > fetching page 1. Is this normal? > > Second, I can't fetch tweets further back than page 41 (with 20 tweets > per page), which is also as far back as I can go on the website. Is > there any way to fetch tweets older than this? If not, will there be? > > I'd really like to make a local copy of my tweets but can't see how to > do so at the moment. > > Many thanks, > Phil > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
