Hot on HuffPost Tech:

See More Stories
Engadget for the iPhone: download the app now
AOL Tech

Should Twitter really count URL characters against you?

Tweet URL Length

URL shorteners, while convenient, are bad for the web. They hide the true destination that they are pointing to, giving bad guys yet another tool in their arsenal, while conditioning web users to blindly trust the links they are clicking on. Further, as the debacle with tr.im showed us, URL shortening services aren't necessarily permanent.

It's no coincidence that the rise in popularity of URL shorteners closely mirrors the rise in popularity of Twitter; Twitter's 140 character limit is the special ingredient that makes Twitter so compelling, but it's also what made short URLs valuable. Some of you will say that short URLs are useful for other reasons - for example, in print. True, but Twitter is by far the place they are used most.

So, with a 140 character limit, how could Twitter eliminate URL shorteners? Well, first, let's look at the reason for the 140 character limit in the first place. It was chosen because Twitter expected SMS messages to be the primary way that users would interact with the service. While there are many users using it that way, their numbers are far eclipsed by the number of users using Twitter on its native web site, or using one of the plentiful Twitter client apps that are available for both desktop computers and mobile phones.


See, here's the thing: the 140 character limit is effectively arbitrary at this point. It was chosen out of convenience (to support SMS), and it turned out to be a magic number that allowed meaningful but necessarily short messages to be composed on the service. Now, I'm not arguing to extend the number of characters Twitter uses - that would undermine Twitter's entire identity. Instead, what I'm suggesting is that characters in a URL should not count against Twitter's 140 character limit. This would completely negate the need for URL shorteners, and would have the positive effect of letting the service's users actually see the URLs that they are clicking on.

Okay, wait a minute, you say -- what about the SMS users? We can't forget about them; they can't handle more than 140 character messages! You're right. And we're not forgetting about them. I propose that Twitter simply intercept URLs that are longer than 22 characters when sending SMS messages and replace them with a placeholder like [reply "URL" for link]. Since the placeholder is 22 characters long, this limits the length a URL could use up, but still gives the SMS user the ability to retrieve a URL if they want to. In fact, this should be a setting that would allow the SMS user to shorten it to simply [URL], and the service would intercept all URLs.

Not counting URLs maintains the spirit of Twitter's character limit, while eliminating Twitter's reliance on 3rd party web-cluttering URL shortening services. But what do you think: should the 140 characters apply to everything including URLs, or just actual human-readable content?

Tags: analysis, character limit, character-limit, CharacterLimit, client apps, client-apps, ClientApps, limit, magic number, magic-number, MagicNumber, Mobile Phones, Mobile-Phones, MobilePhones, short messages, short urls, short-messages, short-urls, ShortMessages, ShortUrls, sms messages, sms users, sms-messages, sms-users, SmsMessages, SmsUsers, twitter, twitter character limit, twitter-character-limit, TwitterCharacterLimit, url, url shortener, url-shortener, UrlShortener

Comments

17