According to my tests, messages will not be truncated anymore!

Instead, you will get the most recent status update as a reply.

Is this a bug or feature?

Also, it seems as if the API now checks for duplicates in your
"backlog" of statuses and not just you most recent tweet.

Previously, only the last tweet was checked:

- Last tweet "test"
- Send new tweet with "status=test" will return the old status (with
the old status_id)

but if you had something like this:

Last tweet "Hello, world."
Second last tweet "test"

Then you were able to create a new tweet with "status=test"!

This is not possible at the moment.

Bug or feature?

I'm getting a lot of complaints from my Twitter client users who
apparently experience both of these new "behaviours" or "bugs" (long
tweets fail, duplicates fail.)

Ole @
On Twitter:

On Oct 15, 8:26 pm, Josh Roesslein <> wrote:
> If you send a message longer than 140 twitter will truncate it and set
> the truncate value on the status to True.
> For duplicates it will just ignore the status.
> Josh
> On Thu, Oct 15, 2009 at 1:20 PM, janole <> wrote:
> > Hi,
> > I just figured out that when calling statuses/update with a text
> > longer than 140 chars, the reply of that API call will be 200 OK with
> > the last status of the user.
> > Wouldn't it be better to return some sort of error message?
> > The same seems to be happening when sending a duplicate tweet.
> > Ole
> > --
> > Jan Ole Suhr
> >
> > On Twitter:

Reply via email to