We’re working to still bring some of these retweet methods to the 1.1 REST API.
You have many alternatives to acquiring this data – especially in real time. We generally favor real-time streaming APIs over the ones that excavate the past (REST). User Streams is your best bet for this in a single-user scenario, while the follow filter on the general streaming API is also a workable alternative for more users. Site Streams, though in beta, is also an excellent alternative.
Tweets a user has issued are in their user timeline. There are methods to determine the retweets for a given status and enough API calls to periodically run through a user’s recently retweeted tweets to collect the delta in retweeters.
The statuses/retweets_of_me method was basically a virtual timeline of data you can assemble yourself.
Can you describe some of the use cases you have where having this in a dedicated method is more useful to you?
