Will there been anything in the tweet payload to let us know that it has replies, or will we need to make requests to the related_results just to find out? Sort of thing I was thinking was in the timeline you have a tweet along the lines of "Dear lazy web, where's the best place to go for pizza in London?", and I was hoping to display "12 replies to this tweet" or "someone has replied to this tweet". Then when clicking on the tweet an extended page would show all the replies.
Thanks Ryan On Sep 21, 12:05 am, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Outstanding. I hadn't even realized this particular API was being made use > of yet here. > > This, and a number of other interesting new APIs are being documented and > readied for wider use now. Any little fun bits you find in advance are fair > game, but until they are documented their behavior, response, and > availability may fluctuate wildly. Keep in mind that #newtwitter's > availability is being gradually rolled out primarily in respect to > scalability, performance & monitoring -- this is also true of the newer > APIs. Until they are announced, please keep any usage of undocumented APIs > cautiously low. > > Taylor > > On Mon, Sep 20, 2010 at 3:55 PM, Abraham Williams <4bra...@gmail.com> wrote: > > The related_results/show/status_id method is returning replies to a > > status_id. > > > Screenshot in the new UI:http://www.flickr.com/photos/4braham/5009432215/ > > > API call: > >http://app.apigee.com/console/apigee-console-snapshots-1283317200000_... > > > Abraham > > ------------- > > Abraham Williams | Hacker Advocate |http://abrah.am > > @abraham |http://projects.abrah.am|http://blog.abrah.am > > This email is: [ ] shareable [x] ask first [ ] private. > > > On Mon, Sep 20, 2010 at 15:30, Taylor Singletary < > > taylorsinglet...@twitter.com> wrote: > > >> Hi Vega, > > >> #newtwitter uses the same API pattern available to all developers for > >> this. When a status contains an in_reply_to_status_id field, then it is > >> considered a reply to a preceding status, which is then fetched by > >> requesting the particular status referenced by in_reply_to_status_id. > > >> This is why you'll see that the implementation in #newtwitter doesn't list > >> *replies to* the current status, but instead the original status that > >> sparked the reply-to. These can be chained but in many cases can never show > >> the whole picture easily. > > >> It would great if we had a statuses/:id/replies method to return all > >> statuses that reference the original status -- would be very useful in this > >> context. > > >> Taylor > > >> On Mon, Sep 20, 2010 at 2:33 PM, Vega <edgardo.v...@gmail.com> wrote: > >> > I have heard the new Twitter only uses the api to display information > >> > if so how does it get Replies to this Tweet? > > >> > Cheers, > > >> > Edgardo > > >> > -- > >> > Twitter developer documentation and resources: > >>http://dev.twitter.com/doc > >> > API updates via Twitter:http://twitter.com/twitterapi > >> > Issues/Enhancements Tracker: > >>http://code.google.com/p/twitter-api/issues/list > >> > Change your membership to this group: > >>http://groups.google.com/group/twitter-development-talk?hl=en > > >> -- > >> Twitter developer documentation and resources:http://dev.twitter.com/doc > >> API updates via Twitter:http://twitter.com/twitterapi > >> Issues/Enhancements Tracker: > >>http://code.google.com/p/twitter-api/issues/list > >> Change your membership to this group: > >>http://groups.google.com/group/twitter-development-talk?hl=en > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
