Hi,

I'm seeing the same thing that Ole is.  Twitter is not truncating the
status, but rather returning the last correctly updated status.

--
Kevin

On Oct 16, 4:58 am, janole <s...@mobileways.de> wrote:
> According to my tests, messages will not be truncated anymore!
>
> Instead, you will get the most recentstatusupdateas 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 oldstatus(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 @ mobileways.de
> On Twitter:http://twitter.com/janole
>
> On Oct 15, 8:26 pm, Josh Roesslein <jroessl...@gmail.com> wrote:
>
>
>
> > If you send a message longer than 140 twitter will truncate it and set
> > the truncate value on thestatusto True.
> > For duplicates it will just ignore thestatus.
>
> > Josh
>
> > On Thu, Oct 15, 2009 at 1:20 PM, janole <s...@mobileways.de> wrote:
>
> > > Hi,
>
> > > I just figured out that when calling statuses/updatewith a text
> > > longer than 140 chars, the reply of that API call will be 200 OK with
> > > the laststatusof 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
> > > s...@mobileways.de
> > > On Twitter:http://twitter.com/janole

Reply via email to