Actually, this data can be obtained pretty easily using Gnip. They have the reply_to_status_id as part of their notification schema. I'm pulling all of this data to maintain the client stats at tweetstats.com/twitter_stats (shameless plug) - as an example, though, I can see that the most replied_to status of the day was http://twitter.com/DonnieWahlberg/status/1455076423
I'm not entirely sure how correct the Gnip data is as I've seen some inconsistencies. But it may simply be that I haven't built in all the necessary redundancy at this point. It should be noted that I believe you can also create a filter on a specific reply_to_status_id (the URL of it) and get HTTP POSTs for any future(?) reference to it. I haven't used that feature myself, hence the question mark. If you'd like some more info on pulling this data on Gnip, feel free to shoot me an email. Their team is all over on Twitter as well and very helpful. Their docs (http://docs.google.com/Doc? id=dpw6zj9_0fdcnttgd), however, are a little confusing. :-\ And if any devs want to collaborate on making this data more easily accessible for the time being, also let me know. :) As mentioned, I already pull the Gnip data, but would need to a) make the retrieval system a bit more robust, b) index it better for this purpose and c) put a pretty front-end on it. dpc On Apr 3, 1:48 pm, Chad Etzel <[email protected]> wrote: > On Fri, Apr 3, 2009 at 4:39 PM, Doug Williams <[email protected]> wrote: > > > It sounds like a number of developers are > > working on rolling their own solution though. > > Holy cow, what an undertaking that would be! It sounded to me like > there are a number of developers with apps waiting in the wings just > dying for this feature to be rolled out... > > If someone figures out a 3rd-party way to make this work, then "Rats > Off To Ya!", but I can't imagine how many API calls that would entail. > If the "in_reply_to_status_id" was at least added to the search > results [1] it would be a heck of a lot easier to roll our own while > we wait. > > [2] > > [1]http://code.google.com/p/twitter-api/issues/detail?id=273 > > [2] -Chad
