http://to/ World's Shortest URL Shortener
51–60 of 150 posts
Re: http://to/ World's Shortest URL Shortener
#52The 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…
Re: http://to/ World's Shortest URL Shortener
#53Earlier 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…
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
#54Earlier 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…
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
#55Earlier 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?
Re: http://to/ World's Shortest URL Shortener
#56Earlier 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.
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
#57Can 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]
Re: http://to/ World's Shortest URL Shortener
#58I also like to know where people are sending me, but that is a secondary concern.
Re: http://to/ World's Shortest URL Shortener
#59Earlier 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.
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);}())