A way to see replies to specific tweets

[Remy Sharp]

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

[Doug Williams]

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 Support
http://twitter.com/dougw

[Martin Dufort]

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 <d...@twitter.com> 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

[Abraham Williams]

If it helps motivate any as soon as this method is added I will be launching a revolutionary app. :)

Abraham

--
Abraham Williams | Hacker | http://abrah.am
@poseurtech | http://the.hackerconundrum.com
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Chicago, Illinois, United States

[Chad Etzel]

On Fri, Apr 3, 2009 at 4:13 PM, Abraham Williams <4br...@gmail.com> wrote:
> If it helps motivate any as soon as this method is added I will be launching
> a revolutionary app. :)

Does that mean we should all be in a spin-wait?
:)

[Martin Dufort]

aren't we all on the same sinking ship then ;-)

[rchouinard]

Oops! Thought I did my research, but apparently not. Thanks for the
info!


-- Ryan Chouinard

On Apr 3, 12:56 pm, Doug Williams <d...@twitter.com> 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

[Doug Williams]

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

[Chad Etzel]

On Fri, Apr 3, 2009 at 4:39 PM, Doug Williams <do...@twitter.com> 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

[Damon P. Cortesi]

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 <jazzyc...@gmail.com> wrote: