The truncation/over 160 characters issue is a relic from an earlier
version of our system, and its behavior may change. The next version
of the API will not include the truncated attribute, and may even
enforce the 140 character limit programmatically.
In the meantime, the only way to see the
It's not a flaw but a feature.
On Fri, Dec 19, 2008 at 9:44 PM, Scott Carter
scarter28m-goo...@yahoo.comwrote:
Hi Alex,
Please refer to a related thread at:
Hi Alex,
Please refer to a related thread at:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/d11a31c7ecf033b/130ed44d6b502e6c?lnk=gstq=160#130ed44d6b502e6c
I am trying to send an update via the API that is greater than 140
characters, but = 160. When I try to
I've never tested it but I would guess the API will always return a
truncated 140 character responses unless.
The other issue sounds like either a bug with how the API saves 140x160
character statuses or a bug with how they are displayed on the web. If the
second it should be taken up with
