Users don't know / don't care about the 140 char limit. If an app allows them to send more than 140, they'll not thing it's a big deal. Twitter can simply communicate that any URL will count for 20 characters, and so, for ex., a tweet could contain 6 veeery long URLs, that would still fit in 140 chars. Not 7, we need spaces between those t.co's ;-)
What I really love in the idea of t.co is that we'll display real URLs, and the only way to do it is to not count those "real URLs" as part of the tweet length. People (myself included) don't really like to see a "bit.ly" link - ever asked yourself what "bit" could mean for, for example, a french speaking grand'pa - they won't necessary click on the link coming from the grand son... ;) Anyways, Rich, I got your point, we need it to be clear from Twitter, but I think we should wait another week or two. ps: Congrats to the API team, good things coming lately. Cheers. On Sep 4, 10:14 am, Rich <rhyl...@gmail.com> wrote: > Personally I feed the 140 should be whatever we send totally ignoring > the t.co factor otherwise it'll confuse end users and look like apps > are broken > > Still waiting for someone from Twitter to talk about hownthe 140 will > work since they reannounced it the other day > > On Sep 3, 9:02 pm, StuFF mc <m...@stuffmc.com> wrote: > > > > > I just want this to be confirmed by @raffi > > > If I understand > > correctlyhttp://groups.google.com/group/twitter-api-announce/browse_thread/thr... > > > This means that I can securely send a 120 (or less) character message > > + a link, no matter how long the link is, it will be translated into > > 20 characters, and so the total being 140 character I'm fine. Right? > > > My Rails app will send "hey this is a message with always > > ahttp://link.com/path/to/resource"; and all I need to check is that "hey > > this is a message with always a " is 120 chars, right? > > > Thanks for confirming this, that would be amazingly cool because it > > would mean I don't need (and nobody would need) to call some t.co API > > to shrink a URL. > > > Then I would only need to count on the updated clients (and > > twitter.com) to display my "http://link.com"; as a text and > > "http://t.co/jhdafkjh"; as a link! Wouldn't be a "big deal" if some > > (most) clients display the t.co as a text :) > > > Cheers. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
