Right now those "modifier" parameters are a bit of a mess, and may or may not work in tandem. Pick one or the other in the meantime, or request the whole thing and filter client-side. Our caching is such that getting the entire response shouldn't be that slow, although I'd understand wanting to cut down the response size for low-bandwidth connections.
On Tue, Nov 11, 2008 at 3:30 PM, buzz <[EMAIL PROTECTED]> wrote: > > Are the page and count parameters intended to interact at all with the > since_id parameter for friends_timeline? What I would like to do is > be able to say "download tweets since this ID, but not more than N > tweets." Right now it appears, if I'm understanding correctly, that > the page parameter does work with since_id, but pages appear to be > restricted to 40 tweets per page and the count parameter doesn't seem > to have any affect. Is there any way to so something like > "since_id=12345" and "count=20," where it would return just the latest > 20 that are after the given ID (and fewer if there aren't 20 after > that ID)? > > -- > Buzz > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
