About URL-Shorteners

06 December 2009

URL-Shorteners are getting popular these days, due twitter’s 140 character limitation. But what happens behind the scenes, if you are opening a url, created by an url-shortener? The shortener takes the request from the browser, looks up the given value of the short url in the database and redirects the browser to the original site. And here is the point, where the trouble comes in:

Short-urls are adding a layer of indirection to the internet, which is not needed in my opinion.

What could Twitter do about short-urls?

People are using url-shorteners, because they are forced to limit themselves to 140 characters. Twitter could implement a different counting mechanism:

By using this behaviour, no one has a real need for short-urls anymore and you will always know, how the real url looks. It should be fairly easy to implement this for twitter, but i think they are not doing this, because people cheat to get more characters in a single by simple typing something like: “http://and-i-also-wanted-to-say-this-and-that.com”. In my opinion, this would be acceptable tradeoff if we could get rid of url-shorteners! You could just unfollow the people who are abusing the now legal long urls for something else and you are done.

My current solution

Because I don’t think twitter will solve the problem with url-shorteners in the near future, I have set up my own with the help of Shaun Inman’s lessn. This solution won’t help to get rid of short-urls, but I am at least no longer dependent of a third party url shortener. I am in control of the short-urls I have posted on twitter and so I will never ever lose a link again, because a short url service abused my trust in their service.

Previous Entry: My New Blog

Next Entry: Change Terminal Colors on Remote Connections