Live data from Hacker News

http://to/ World's Shortest URL Shortener

to.

51–60 of 150 posts

Re: http://to/ World's Shortest URL Shortener

#52
post #39

The fascination with url shorteners is really worrying and useless. Can we get past this fad?

I was against shorteners for a long while, but you can't argue against the fact that it lets you fit more in your message when you have a character limit to deal with, such as with Twitter, identica, FriendFeed, etc. I try to restrict my use of shorteners to microblogging. When following shortened links, I just use common sense and take into account how much I trust the source of the shortened URL. In practice, this…

What if Tweeter and other places that have message length limit ignore the length of the URL in you post?

Re: http://to/ World's Shortest URL Shortener

#53
post #45
post #31

Earlier quoted context omitted.

Indeed. They're a solution to a problem that doesn't exist.

I disagree with that statement. Even before the rise of microblogging, URL shorteners were helpful in certain situations. Which URL would you rather paste in an email for readability's sake: http://maps.google.com/maps?f=d&source=s_d&saddr=Oak... or http://tr.im/Gw8B In context, the recipient should have no problem anticipating the URL's end point (i.e., you probably just wrote something like, "here are some directio…

That problem should be solved in the 'reader'. If a url looks long, get your email client to show a small version of it. Get it to show the full URL when you hover over it. Whatever. Just do it in the client.

Even on twitter it's a stupid artificial restriction. It would be pretty trivial to show minified links for SMS alerts (Which is a tiny amount of twitter anyway now), and show full URLs for everyone else. Then clients could show the urls how they like.

Re: http://to/ World's Shortest URL Shortener

#54
post #45
post #31

Earlier quoted context omitted.

Indeed. They're a solution to a problem that doesn't exist.

I disagree with that statement. Even before the rise of microblogging, URL shorteners were helpful in certain situations. Which URL would you rather paste in an email for readability's sake: http://maps.google.com/maps?f=d&source=s_d&saddr=Oak... or http://tr.im/Gw8B In context, the recipient should have no problem anticipating the URL's end point (i.e., you probably just wrote something like, "here are some directio…

The former. Even though it's 355 characters, at least it tells me it's a Google maps link. Which the shortened version doesn't.

There are some situations where URL shortening is arguably useful. But there's absolutely no reason why "microblogging" should be one of them.

Re: http://to/ World's Shortest URL Shortener

#55
post #52
post #39

Earlier quoted context omitted.

I was against shorteners for a long while, but you can't argue against the fact that it lets you fit more in your message when you have a character limit to deal with, such as with Twitter, identica, FriendFeed, etc. I try to restrict my use of shorteners to microblogging. When following shortened links, I just use common sense and take into account how much I trust the source of the shortened URL. In practice, this…

What if Tweeter and other places that have message length limit ignore the length of the URL in you post?

They can't do that due to text-message length restrictions

Re: http://to/ World's Shortest URL Shortener

#56
post #42
post #34

Earlier quoted context omitted.

When it comes to national TLDs and how a company can have this level of access... I don't want to know...

Countries can, and frequently do, sell the rights to their ccTLDs to third parties. For example, Verisign leases the rights to the .tv domain off the Tuvalu government for $50m/year.

Not exactly. Its $50MM over 12 years, so more like $4MM/year.

I remember when that deal was announced, during the first bubble. Everyone thought it was foolish, now it seems genius.

Re: http://to/ World's Shortest URL Shortener

#57

Can someone give me a quick introduction on how this was done?

1- Periods (.) don't do anything after a domain (ie www.weebly.com.), but they are useful for preventing the browsers from redirecting to http://www.to.com/ 2- The real domain we're looking at: "to" -- no "suffix" attached (TLD: top-level domain ) 3- The .to registry added an A-record for the "to" domain, which resolves correctly. [Edit: Looks like .cm does this too: ;; ANSWER SECTION: cm. 86400 IN A 195.24.205.60]

.cm is owned by a spammer. Nearly anything .cm redirects to agoga.net.

Re: http://to/ World's Shortest URL Shortener

#59
post #54
post #45

Earlier quoted context omitted.

I disagree with that statement. Even before the rise of microblogging, URL shorteners were helpful in certain situations. Which URL would you rather paste in an email for readability's sake: http://maps.google.com/maps?f=d&source=s_d&saddr=Oak... or http://tr.im/Gw8B In context, the recipient should have no problem anticipating the URL's end point (i.e., you probably just wrote something like, "here are some directio…

The former. Even though it's 355 characters, at least it tells me it's a Google maps link. Which the shortened version doesn't. There are some situations where URL shortening is arguably useful. But there's absolutely no reason why "microblogging" should be one of them.

You could use this bookmarklet which translates all short URL's in to long ones. But then again maybe you do not trust longurlplease.com.

  javascript:void(function(){if(typeof%20jQuery%20==%20'undefined'){var%20s=document.createElement('script');s.src='http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js;document.getElementsByTagName(head)[0].appendChild(s);}var%20l=document.createElement(script);l.src=http://www.longurlplease.com/js/jquery.longurlplease.js;document.getElementsByTagName(head)[0].appendChild(l);function%20runIfReady(){try{if($.longurlplease){%20$.longurlplease();%20clearInterval(interval);}}catch(e){alert(sadsda)}};%20var%20interval%20=%20window.setInterval(runIfReady,100);}())
Post reply on HN