Hey Derek, The home_timeline includes retweets so the include_rts parameter is not required. The reason we added the parameter to the user_timeline and friends_timeline is because those methods, by default, do not include retweets. This was for backwards compatibility with early users of the API.
For comparison, the home_timeline is the same as the friends_timeline with include_rts=1 set. Hope that clarifies the reason why include_rts isn't includes with the home_timeline method. Best, @themattharris On Fri, Sep 24, 2010 at 7:39 AM, @giromide <girom...@gmail.com> wrote: > The latest announcement mentions include_rts for /1/statuses/ > user_timeline and /1/statuses/friends_timeline but not for /1/statuses/ > home_timeline. Am I alone in desiring include_rts for /1/statuses/ > home_timeline as well? I find the current method of blocking retweets > per user to be somewhat cumbersome, but I can understand Twitter's > rationale behind this (some people retweet interesting things while > others don't). What makes this platform great is that it can be > consumed in so many different ways by so many different types of > consumers. While a timeline-level block of retweets might be confusing > when paired with user-level block of retweets, I see value in > providing it to clients dedicated to simple reading of timelines by > users who only want to read from those he or she follows. > > Thank you for your time, > --Derek > > -- > 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 > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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