Hi Lagden, Unfortunately, our API is architected in a way that requires us to perform the pagination calculations before filtering out things like retweets. This is expected behavior. It's best to consider the count parameter as a "hopeful" parameter. You will get, at most, the amount you've asked for.
Taylor On Tue, Oct 26, 2010 at 6:36 AM, Lagden <lag...@gmail.com> wrote: > Hi, > > > I have the follow situation on my timeline: > > xx: rts -> retweet > xx: rts -> retweet > xx: abc -> tweet > xx: def -> tweet > > I am using API and when I make a request: > > > http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=xx&count=2&page=1&include_rts=true > > works fine, but when I make with include_rts=false: > > > http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=xx&count=2&page=1&include_rts=false > > The request does not show the RTS, but it is included in the count! > > Should not begin from "abc"? > > > Regards!! > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
