One of the main confusions and criticisms about the retweet API was
around what happens when a given tweet is retweeted multiple times.
The explanation was that developers need to do their own retweet
collapsing. If N people retweet a given tweet, you'd get N instances
of that same tweet in the appropriate retweet timeline and the home
timeline. You would then have to do your own internal book keeping
about whether that tweet had already come in. If it hadn't you'd
display it for the first time. If it had you'd update the already
Asking developers to collapse retweets in timelines is onerous,
complicated and confusing. We're not going to do it that way. We are
going to add a resource that gives you all retweets for a given tweet.
In timelines you will get only the first retweet. You can then request
all retweets for that tweet at any time to get up to 100 retweets that
have been created for it.
Here is the documentation for the new resource, statuses/retweets:
Sincere apologies if you've already written collapsing logic for
retweets. Beta releases are beta releases and I think the retweet API
is a lot better without the onerous collapsing requirement.
To give you some ideas of how you can use the API to display retweets,
here is a recent mock up of one of the potential UIs for the retweets
timeline on twitter.com:
If you've got questions, find bugs, or have any kind of feedback, get
in touch via the dev mailing list, send an @reply to @twitterapi or
jump into the #twitterapi IRC channel on irc.freenode.net.
Twitter Platform Team