Message from discussion in_reply_to_status_id
Content-Type: text/plain; charset=ISO-8859-1
Received: by 10.90.98.12 with SMTP id v12mr73611agb.25.1218853112490; Fri, 15
Aug 2008 19:18:32 -0700 (PDT)
Date: Fri, 15 Aug 2008 19:18:32 -0700 (PDT)
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
rv:1.9) Gecko/2008061004 Firefox/3.0,gzip(gfe),gzip(gfe)
Subject: Re: in_reply_to_status_id
From: Ray Grieselhuber <rgrieselhu...@gmail.com>
To: Twitter Development Talk <firstname.lastname@example.org>
Is this change related at all to the fact that many users (including
myself) can no longer see their replies, either via the web client or
the API? When will this be fixed?
On Aug 15, 2:34=A0am, "Alex Payne" <a...@twitter.com> wrote:
> I'm happy to announce a minor change to the API that should have a
> major impact on the Twitter community. =A0The /statuses/update method
> now takes an optional parameter: in_reply_to_status_id. =A0As you might
> guess, this allows API clients to specify which status a status to be
> posted is in reply to, rather than our system assuming that it's in
> reply to the last message posted by the user specified by "@username".
> If your client posts statuses, please consider making use of this
> feature. =A0By convention, we'd like to continue to use "@username" at
> the beginning of messages that are replies, but specifying the
> in_reply_to_status_id parameter will override the guess about the
> in_reply_to_status_id attribute that our system makes. =A0Yes, this does
> mean that you could post a message that appears to be a reply to Alice
> while it's actually a reply to Bob; that's fine, as I'm sure there's a
> use case for it out there.
> We hope this addition will allow for more accurate conversations on
> Twitter. =A0I can't wait to see what you all do with it!
> Alex Paynehttp://twitter.com/al3x