> On Sat, Oct 17, 2009 at 10:41 AM, Marc Mims <marc.m...@gmail.com> wrote:
> > Updates longer than 140 characters should be forcibly truncated
> > according to the documentation.  Instead, the update call returns with
> > a 200 status and the payload contains the prior update.
> >
> > Has there been a change to the API or is this a bug.

On Sat, Oct 17, 2009 at 05:15:42PM -0500, Josh Roesslein wrote:
> This is a change in the API confirmed by one of twitter's API members.
> The docs should be updated soon.

In that case, is there any change (planned or current) which will
indicate when this has happened, or if the update has been rejected for
any other reason?  Failing silently does not seem appropriate,
particularly when the failure returns the user's previous status.

-- 
Dave Sherohman

Reply via email to