i can't speak as to whether we're going to put them into the user_timeline or not -- although, i would suspect no, as it has the potential for breaking legacy applications, and it is something we could revisit in a future version of the API (e.g. a hypothetical api.twitter.com/2). again, for clarity, i'm don't know for sure.
if developers would like the equivalent of a user_timeline that has retweets in it, then they could easily fetch the following two timelines: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-retweeted_by_me and merge them together to form a "virtual timeline". On Dec 31, 2:24 am, Jesse Stay <jesses...@gmail.com> wrote: > On Tue, Dec 22, 2009 at 10:42 AM, Raffi Krikorian <ra...@twitter.com> wrote: > > go code something interesting, and we will be here to support you. (of > > course, if we missed something, as we are arguing about in the RT case, we > > will work with you all to get it to be what the community needs). > > So does this mean RTs will be restored as is being requested? I don't think > anyone is questioning that you need to be creative with the Twitter API. > > Jesse
