| Issue 273: | in_reply_to_status_id not available from search.twitter.com json results. | |
| 8 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
What's the problem you're seeing? In order to find the original message being replied to from the reply in a search.twitter.com entry, one would have to do an API lookup on the status and then do an API lookup on the in_reply_to_status_id status. This means using search to find original messages results in an extra API lookup. |
||||||||||
,
Feb 09, 2009
Issue 272 has been merged into this issue. |
|||||||||||
,
Feb 09, 2009
This is something we'll be adding when we unify the output formats in the next verison of the API. I think the actual usage you're talking about might be the same as issue #142 (Conversation API).
Status: Accepted
Owner: m...@twitter.com Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low Milestone-V2 |
|||||||||||
,
Feb 09, 2009
Just to clarify, the Conversation API looks promising but my use would be slightly different. I don't do a reverse lookup like that. I am actually interested in searching for a tweet containing a certain phrase that is directed at someone and then looking up the original message. The way the API is set up right now allows me to do that fairly easily, but it involves an extra API call because in_reply_to_status_id isn't in the search results. Keep up the good work and I look forward to future enhancements. |
|||||||||||
,
Apr 21, 2009
This issue has been recorded in the future roadmap: http://apiwiki.twitter.com/V2-Roadmap
Status: Moved
|
|||||||||||
,
Apr 21, 2009
Marking "Invalid" so these issues don't clutter the main view of issues. All are tracked on http://apiwiki.twitter.com/V2-Roadmap
Status: Invalid
|
|||||||||||
 Sign in to add a comment
|
|||||||||||
