Abraham, you are right that I had the wrong understanding of the parameter. When I read "the timeline will contain native retweets in addition to the standard stream of tweets" I didn't realize it meant native retweets of the mentions themselves. It makes sense to me now but I am not sure how that parameter is useful to anyone :-) It's a bit surprising to hear that any REST API client that wants to provide a unified view of mentions/retweets (which makes sense to most users) has to make two calls and merge the results, but I guess that's what I need to do! Thanks,
-Anil On Feb 10, 2:06 am, Abraham Williams <4bra...@gmail.com> wrote: > I think you have the wrong idea of what include_rts does. Include_rts is > designed to include native retweets in timelines where default inclusion > would break. For example /statuses/user_timeline expects all tweets to be > from a user A. But if that user A has retweeted user B then user Bs tweets > can be included user As user_timeline with include_rts. Include_rts has no > effect on /statuses/mentions because the original tweet is already included > due to the fact it is a mention. > > Abraham > ------------- > Abraham Williams | Hacker Advocate | abrah.am > @abraham <https://twitter.com/abraham> | github.com/abraham | blog.abrah.am > This email is: [ ] shareable [x] ask first [ ] private. > > > > On Wed, Feb 9, 2011 at 21:00, Adam Duke <adam.v.d...@gmail.com> wrote: > > I've seen the same behavior with the include_rts parameter. I have > > tried passing the values 'true', 't', and '1' with no success. > > > On Feb 8, 7:15 pm, Anil Chawla <ani...@gmail.com> wrote: > > > It's been a while but I want to follow up on this because we still > > > have the issue. Is anyone able to pull "native" retweets when calling > > > the "statuses/mentions" endpoint? > > > > An indication that "includes_rts" either works for you or doesn't work > > > would be great. Thanks, > > > > -Anil > > > > On Dec 14 2010, 11:44 am, Anil Chawla <ani...@gmail.com> wrote: > > > > > I've also been facing this issue for quite a long time. I've told > > > > myself that this can't be a problem with the API (since nobody else is > > > > complaining) but I can't see what is wrong on our end. For example, I > > > > have the following status that was retweeted a few times: > > > > >http://twitter.com/#!/anilchawla/status/14437959797313536 > > > > > This is the request URL that is generated when I request my mentions > > > > using count=200, include_rts=true, and since_id = 13978625736970241 > > > > (OAuth tokens omitted): > >https://api.twitter.com/1/statuses/mentions.json?count=200&include_rt... > > > > > The four mentions of the above status are not present in the response > > > > even though those retweets and the original status have an ID greater > > > > than since_id. Omitting "count" and "since_id" does not make a > > > > difference. As a work-around, we have to pull both statuses/mentions > > > > and statuses/retweets_of_me and merge them together. It's hard to > > > > believe that everyone else has been doing the same and ignoring this > > > > API parameter. Any idea what the issue is? > > > > > -Anil > > > -- > > 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
