If you take a look at the payload of a retweet in the examples, each retweet has the id of the original tweet as well as details about the retweet (who retweeted it, when and what the id of the retweet is). That information, specifically the retweet's id, should be sufficient for your purposes.
On Wed, Sep 2, 2009 at 2:58 PM, hansamann<sven.hai...@googlemail.com> wrote: > > Hi all, > > this questions might have been asked already, but a quick search in > this mailing list did not lead me to a clear response... so I > apologize if this topic was discussed in detail already. > > My question: > > - if a tweet is retweeted several timese, e.g. tweet X is retweeted by > my friend A and my friend B, it is likely these retweets are not > taking place the same time. > > - my assumption and question is if the 2 retweets in this case show up > as two tweets in the home timeline. What troubles me is how I can > detect that a tweet was retweeted. I intend to save the last pulled > statusId and then just pull tweets from the home_timeline from the > last statusId. I hope to get the 'new retweets' as they happen as new > people are retweeting. If the api will aggregate the retweets under > the stausId of the original message, I will not be updated of new > retweets in this case. On the other side, if a new retweet will add > the original status a second time (possibly with the new total > retweets, e.g. several retweet_details) then I track the retweet > count. > > What do you think? > > Cheers > Sven > -- Marcel Molina Twitter Platform Team http://twitter.com/noradio