Martin, The issue is tracked for the V2 milestone which means it's not a priority at the moment. It sounds like a number of developers are working on rolling their own solution though. Hopefully they can be convinced to make those results available via an API to keep everything moving forward.
Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 3, 2009 at 1:09 PM, Martin Dufort <[email protected]> wrote: > > Doug: This has been opened by Craig a number of months ago. Any ETA > for inclusion in the Twitter API ? Thanks - Martin > > On Apr 3, 12:56 pm, Doug Williams <[email protected]> wrote: >> Remy, >> A track already exists for this request [1]. >> >> 1.http://code.google.com/p/twitter-api/issues/detail?id=142 >> >> Doug Williams >> Twitter API Supporthttp://twitter.com/dougw >> >> >> >> On Fri, Apr 3, 2009 at 9:53 AM, Remy Sharp <[email protected]> wrote: >> >> > Hi, >> >> > I've been looking around the API (and the search.twitter.com pages) >> > and I believe it's not possible to find all the tweets that are in >> > direct reply to a specific status_id. >> >> > I know I can get all the replies *since* a specific status_id, but >> > this gives me the latest replies - so if it was some time ago I can't >> > see the real replies. >> >> > It would be really useful to see direct replies to X status_id to be >> > able to track a conversation. >> >> > I've also tried the search.twitter.com API, but it looks like the >> > since_id breaks the request: >> >> > Specifically since there's the 'in_reply_to' key in the return object >> > from the statuses. Even better if we didn't need to have an >> > authenticated session to get the conversation. >> >> > Anyway - be great if it was considered for the API - happy to add the >> > request to the issues log if you think it's worth while. >> >> > Cheers, >> >> > -- Remy Sharp >
