| Issue 142: | Conversation API | |
| 53 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Please add the ability to search for replies to a given tweet ID. The use case for this is when someone asks a question like "What's the best place to get T-shirts printed in small runs?". The only way to search for answers is by using the original poster's screen_name, which contains a lot of noise in the results. Specifying the original tweet's ID would be much more accurate (now that clients like Twitterrific are starting to set it when replies are posted.) More info in this discussion thread: <http://groups.google.com/group/twitter-development-talk/browse_thread/thread/251c78147a0c7d88?hl=en> |
||||||||||
,
Nov 17, 2008
Changed title to make it clear this is a request for a conversation/thread API
Summary: Feature Request: Ability to pull replies to a given status
Labels: -Type-Defect Type-Enhancement |
|||||||||||
,
Dec 01, 2008
Changing title again for maximum literalness.
Summary: Conversation API
Status: Accepted Labels: -Priority-Medium Priority-Low |
|||||||||||
,
Dec 16, 2008
(No comment was entered for this change.)
Labels: Milestone-V2
|
|||||||||||
,
Dec 22, 2008
Additional request on the dev list for RSS/Atom feeds of this data http://groups.google.com/group/twitter-development-talk/browse_thread/thread/b46e87f05101645b |
|||||||||||
,
Apr 05, 2009
A brief note that this is possible utilizing Gnip (if I'm reading the original request properly). For global usage, you'd have to pull their notification stream on a constant basis, but you can also create a filter on a specific tweet and get replies to that tweet. It's not ideal, but can serve as a temporary workaround. |
|||||||||||
,
Apr 20, 2009
(No comment was entered for this change.)
Owner: alexfpayne
|
|||||||||||
,
Apr 21, 2009
This is a feature that we recognize is desired. However until the product (Twitter.com) supports this form of conversation grouping, the API cannot provide access to this data at scale. Therefore, we are going to close this ticket and reopen it when the main product supports delivery with the type of performance demanded by API clients.
Status: WontFix
Labels: -Milestone-V2 |
|||||||||||
,
Apr 22, 2009
Not even getting a search param for in_reply_to_status_id? |
|||||||||||
,
Apr 22, 2009
Yeah, just adding a in_reply_to_status_id to the search results would be incredibly useful. I'd hate to see that dismissed with the rest of it. |
|||||||||||
,
Apr 22, 2009
Yep, and changing the search would be different since it's an entirely separate app, and it certainly receives that data via XMPP. |
|||||||||||
,
Jun 01, 2009
Issue 630 has been merged into this issue. |
|||||||||||
,
Jun 04, 2009
Aw sad to see it being closed. Could make a really good use of it :( |
|||||||||||
,
Jul 05, 2009
Issue 693 has been merged into this issue. |
|||||||||||
,
Jul 09, 2009
Issue 822 has been merged into this issue. |
|||||||||||
,
Jul 12, 2009
This method would be very useful, but I think simpler things such as a count of the number of replies would be useful whenever the status is retrieved in the existing APIs whereas this method requires a completely new method. |
|||||||||||
,
Jul 12, 2009
@adman.com - I completely disagree. If you had the number of replies, and were able to show that number it would then highlight this issue even more, i.e. there's no point in showing a number of something you *can't* show. We can't even dig through the search API for these results because the search API response doesn't contain the in_reply_to id. Here's a demo I've written showing the functionality we're waiting for, and it's a total hack and completely limited to your *own* tweets that have replies [which sucks :-( ] http://remysharp.com/demo/twitter_replies/ Anyway, still looking forward to the day this is implemented :-) |
|||||||||||
 Sign in to add a comment
|
|||||||||||
