Issue Type: Improvement Created: 2009-07-30T10:41:54.000+0000 Last Updated: 2009-09-18T10:02:14.000+0000 Status: Resolved Fix version(s): - 1.9.3 (22/Sep/09)
Reporter: G Cohen (firstname.lastname@example.org) Assignee: Pádraic Brady (padraic) Tags: - Zend_Service_Twitter
Related issues: Attachments:
Having a url in your message may make the message longer than 140 characters, which throws an error, but twitter will shorten the URL, so maybe it's best to leave it up to them to deal with the length of the string.
Posted by Ralph Schindler (ralph) on 2009-09-14T07:09:43.000+0000
Does twitter have an API for sending a message over for potential shortening before committing? How do other libraries handle this? Wouldn't you get an error/exception from the service if its over 140? It seems like it would be sufficient perhaps?
Posted by Jon Whitcraft (sidhighwind) on 2009-09-14T08:20:49.000+0000
I don't believe that the api will shorten the url. I know the web interface does but that could be their own doing on their front end code. According to the documentation here: http://apiwiki.twitter.com/Twitter-REST-API-Method… they just forceably truncate the status if it's over 140 characters.
Posted by Pádraic Brady (padraic) on 2009-09-18T10:02:11.000+0000
Added to r18251:
Increased initial limit to 246 characters based on: a) Maximum count displayable from a non-truncated status b) Counts characters when status is a UTF-8 html encoded string (entities chars are included in count) c) Statuses over 140 characters are still worth avoiding, there is no guarantee a client will link the web status page showing the untruncated message.
Have you found an issue?
See the Overview section for more details.