I didn’t want to start a separate discussion as I think it relates to Bruno’s question. Or more specifically, the usage of include_rts parameter on statuses/mentions_timeline API. I have seen other discussions around this topic but this one seems closest.
To frame the question we are in the process of migrating from the legacy v1 to equivalent v1.1 APIs. According to the documentation, the legacy v1 statuses/metions, statuses/user_timeline and statuses/home_timeline APIs indicate that they support the include_rts parameter (although we found that the statuses/mentions API didn’t seem to behave as expected). In the case where the authenticated user retweets a mention, it was expected that the retweet would be returned with the nested retweeted status (mention) as is the case in the other API calls. However, it doesn’t seem to matter if this parameter is set as the mention is always returned as a top level status.
We have verified that the equivalent v1.1 statuses/user_timeline and statuses/home_timeline APIs support the include_rts parameter and behave as expected (although the parameter isn’t actually documented on the latter API nor on the statuses/mentions_timeline API).
The question is if it is planned for the v1.1 statuses/mentions_timeline to expose the behaviour above? The workaround with the legacy API was to call the statuses/retweeted_by_me API and update the statuses accordingly if a matching retweet was found. Obviously we would prefer not having to make additional calls to get this information. That and the fact that the statuses/retweeted_by_me API doesn’t seem to have been migrated yet. So worst case, is there a plan to migrate the statuses/retweeted_by_me API at some point?
Sorry for the long winded question but we would appreciate any feedback.
Thanks in advance.