Most of the APIs will return at most 20 results, not exactly 20 results. Inappropriate tweets, such as deletions, etc., are filtered out at read-time. I think some code paths attempt to fix up the cached vector, where possible, but not all can and not all do. You can see this happen when a subsequent identical call returns more values.
I'm sure there are all sorts of edge cases that I'm not aware of, and things constantly change, but, In the end, if you need to display exactly 20 tweets, you might just need to loop until you receive 20 tweets. -John Kalucki http://twitter.com/jkalucki Infrastructure, Inc. On Tue, Feb 2, 2010 at 4:15 AM, Horse <chris.horsn...@meloncreative.co.uk> wrote: > For some reason when I request my user_timeline it is only returning 7 > results. Also if I use count to try and get 1 or 2 results it doesnt > show any. I definitely have more than 7 tweets, so can someone point > me in the right direction? > > http://twitter.com/statuses/user_timeline.xml?screen_name=meloncreative > > Also on my personal account it returns 18 > > http://twitter.com/statuses/user_timeline.xml?screen_name=h0rseh0rse > > Is it doing something strange with the RT's, as it could be extracting > them from the 20 but not actually showing a full 20 results. > > Bit confused, can someone confirm? >
