hi jeff. yup - we're definitely guilty for not yet putting an error code for when we reject a tweet due to length.
we do, however, have this page http://apiwiki.twitter.com/Counting-Characters that we put up a month ago that explains how to count your characters correctly and to help define what twitter means by "140". On Wed, Feb 3, 2010 at 2:00 AM, Jeffrey Friedl <jfri...@gmail.com> wrote: > RE this thread: > > > http://groups.google.com/group/twitter-development-talk/browse_thread/thread/cd95ce07be341223/e174915c3ea94e69?lnk=gst&q=140 > > It's been three months since an apparently-silent not-backwards- > compatible API change went into effect that causes tweets longer than > 140 characters to be ignored, but generate a success reply with no way > to know for sure whether the tweet was actually accepted, or why it > might have been ignored if it was. > > The docs haven't even been updated... they still say that too-long > tweets will be forcefully truncated (and marked as such in the reply). > > Since Twitter can diddle the text of the tweet, and it's apparently > unclear exactly what Twitter might count as a character, there seems > to be no way that an app can know ahead of time whether a tweet is > within the limits, and no easy way to find out whether it's actually > been accepted. > > Sigh. > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi