Craig, Great questions. The in_reply_to_status_id will be honored only if the value is a status_id that was authored by a user that is also mentioned in the tweet. Therefore, if you include a status_id for this parameter and that is either 1) invalid or 2) does not belong to a user mentioned in the tweet, the field will be discarded.
Your second question then becomes pretty intuitive when coupled with our recent change to the in_reply_to_status_id field. If this field is valid by the rules above, it will produce a "in reply to <user>" in the Web GUI. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Mar 30, 2009 at 6:26 PM, Jakk <specto...@gmail.com> wrote: > > I've been waiting for this for so long, thank you! > > On Mar 30, 8:39 pm, Doug Williams <d...@twitter.com> wrote: > > Devs, > > Before today calls to statuses/replies [1] would return only tweets that > > were prefixed with a @username. As clients began to recognize the value > in > > mentions of a @username anywhere in the tweet, they opted to perform a > > search for @username to get the superset. > > > > Twitter agrees [2] that the definition of a reply has changed, and as > such, > > calls to statuses/replies contain any tweets that include a mention of > the > > authenticating user. > > > > If your client has been using the Search API to retrieve @replies, you > > should begin to migrate to statuses/replies method as it now best > practice. > > > > 1.http://apiwiki.twitter.com/REST-API-Documentation#statuses/replies > > 2.http://blog.twitter.com/2009/03/replies-are-now-mentions.html > > > > Code on, > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw >
