News for hackers. Stuff that matters.
Re:Bit.ly was down by frankdenbow on Sunday January 13, 2013 @08:25AM (#5050695)
In general, url shorteners seem bad for the web. Something so critical to the structure of the web as links should not have a single point of failure like this.
Re:Bit.ly was down by Tichy on Sunday January 13, 2013 @09:32AM (#5050812)
I suppose for url shorteners to go away, the web standards should provide for some way to provide content providers with statistics. That is what URL shorteners are most often used for, and until there exist alternatives, they'll continue to be used.

Wasn't there even an attribute on links for a while, which created an outcry because it would send statistics of clicks to another URL? Don't remember the details. I understand why it created an outcry, but the fact is, people will be tracked no matter what :-(

Re:Bit.ly was down by calpaterson on Sunday January 13, 2013 @09:58AM (#5050864)
Do you mean the "Referer" header? It's still used, but HTTPS often doesn't pass it.
Re:Bit.ly was down by raverbashing on Sunday January 13, 2013 @10:24AM (#5050920)
No

Referer works for the 'end of the link' (the webserver serving the page)

Bitly and others provide statistics on the 'clicking' of the link, that is, the amount of people that clicked the link (usually published on social media, but not necessarily, by someone that's not the original content host). That's the impact they're trying to measure.

And sometimes it is the content host that published these links, because of a limited capability in deriving these statistics server side (even though Google Analytics goes a long way)

Re:Bit.ly was down by Tichy on Sunday January 13, 2013 @10:26AM (#5050927)
The problem with Referer is that only the server/host get's to see it. Often people publish their stuff on other people's platform, and can't access the stats.
Re:Bit.ly was down by jyap on Sunday January 13, 2013 @08:52AM (#5050741)
I agree.

In dealing with anti-spam techniques, URL shorteners are used to obfuscate bad links all the time.

There are only 2 use cases:

- Used to actually shorten links, say in emails. To me, this isn't a valid use case. I always dump the whole URL.

- Tracking and analysis. For example, Twitter injects t.co links into every Tweet with links for tracking purposes. In the case of Bit.ly, click analytics is their business model (http://www.enterprise.bitly.com).

Re:Bit.ly was down by pavel_lishin on Sunday January 13, 2013 @11:56AM (#5051133)
The first case you mention is actually very useful in IRC, especially in clients that break up URLs into multiple lines.

Compare:

    https://maps.google.com/maps?saddr=1120+Avenue+of+the+Americas,+New+York,+NY&daddr=Yankee+Stadium,+East+161st+Street,+Bronx,+NY&hl=en&ll=40.792239,-73.955154&spn=0.10371,0.157757&sll=40.802895,-73.924084&sspn=0.103693,0.157757&geocode=FcHhbQIdhRqX-ynJiS1XVVjCiTFFAV5BZkL2Ug%3BFZgBbwIdnPiX-yEIHppV2cNASSlxaedaLPTCiTEIHppV2cNASQ&dirflg=r&ttype=dep&date=01%2F15%2F13&time=1:00pm&noexp=0&noal=0&sort=def&mra=ls&t=m&z=13&start=0
to http://is.gd/lerDux - especially when you're looking at it in an IRC client: http://i.imgur.com/mqqRo.png
Re:Bit.ly was down by PJones on Sunday January 13, 2013 @05:40PM (#5052188)
In cases like that I'd use the short url that Google provides (http://goo.gl/maps/4y1Xg). If Google is down then you can't view the map anyway.

Sites providing their own short urls isn't much of a problem as far as I can see.

Re:Bit.ly was down by kmfrk on Sunday January 13, 2013 @08:43AM (#5050719)
If the biggest URL shortener can't figure out how to stay afloat, none of them can.

Definitely roll your own, if you need to. I just need to figure out how to do it for static websites, since they don't have IDs that can be mapped to a shorturl.

Re:Bit.ly was down by udp on Sunday January 13, 2013 @09:24AM (#5050795)
Or just use direct links, instead.
Re:Bit.ly was down by covati on Sunday January 13, 2013 @08:49AM (#5050731)
As a general idea of routing all traffic through one point, yes. However, as a marketing tool to track traffic, they are quite valuable. Sadly, optimal network routes and other considerations take a bake seat to making money.
Re:Bit.ly was down by jhund on Sunday January 13, 2013 @10:45AM (#5050966)
As far as I can tell, the two primary reasons for using URL shorteners are the ability to

a) share long URLs via twitter and

b) track clicks on shared links.

The downsides to URL shorteners are:

a) single point of failure for links. This one is very significant, more below.

b) obscurity of a link's destination. This is mostly annoying and enables spammers to obfuscate their spam URLs.

We can't overestimate the seriousness of having a single point of failure on web links: URL shorteners are a man-in-the-middle, or a choke point for the connection to a web page. All traffic has to go through the server that hosts the shortened link. And if that man-in-the-middle for some reason doesn't want to, or can't redirect to the next destination, your link is broken. And nobody can tell where it pointed to. So not only is the link broken for as long as the man-in-the-middle is not available, but nobody can find out where it led to originally. There is no workaround! So why would the man-in-the-middle not redirect the link? Here are a few reasons:

* the server is down for technical reasons. This happens all the time, most recently with bit.ly.

* the company that runs the server goes out of business. What do you know about the financial situation of your link shortening service provider? How can you be sure that they will still be paying for and looking after their servers in a month, a year, in 10 years?

* somebody who doesn't like what you are linking to makes sure that your links are not being redirected. The incredible democratic power of the internet is being subverted by installing choke points on the internet that allow selective disabling of certain locations on the internet. And how convenient would be the ability to disable all links that point (via a choke point) to an unwanted URL. Not only could somebody break those links, but they could also destroy the information about the location of that unwanted URL with an encrypted string like "bit.ly/SDJHGe65sef". Nobody would know where the link pointed to without access to bit.ly's database.

* the URL shortening service's DNS stops working. Bit.ly is registered in Libya. Who knows what regime will be in power there in a few months. Will they continue to allow Western companies to use '.ly' TLDs?

By sharing shortened links on twitter, you're not dealing with one man-in-the-middle, but two: Your own shortening service and Twitter's t.co shortener. So you have two single points of failure in series. You just doubled the probability of your links being broken.

It seems to me that the disadvantages and risks far outweigh the benefits of using shorteners (at least for links that I hope to be around for a while).

So what are the alternatives to using shorteners? Twitter already distinguishes between displayed and expanded URLs, so there is really no need to apply choke-point shortening. The click tracking is a bit more complex. If you share links on a platform you control, you could do something similar to what google does with their search results click tracking. Or, if you want to share your links on somebody else's platform, make sure that the platform can provide you with non-invasive click analytics.

Re:Bit.ly was down by matb33 on Sunday January 13, 2013 @11:26AM (#5051047)
Does a URL shortener service exist that compresses the URL instead? It wouldn't be as short of course, but then you could recover the original URL yourself if the service is down. A browser could, should this become a popular enough method, be capable of detecting such compressed URLs and doing the decompression and redirect
Re:Bit.ly was down by kmfrk on Sunday January 13, 2013 @11:45AM (#5051097)
Depending on how obscure your links are, you can use .htaccess to go from mysite.com/blog/2012/05/05/somethingsomethingsomething to mysite.com/s/1231, assuming it's not a static website.

Stack Overflow do the same for instance.

Re:Bit.ly was down by pavel_lishin on Sunday January 13, 2013 @11:54AM (#5051128)
I think he's talking about something that shortens any arbitrary link.
Re:Bit.ly was down by kmfrk on Sunday January 13, 2013 @01:12PM (#5051328)
That was my impression, too, but I just wanted to cover a - comparably - dead-simple solution, since we sometimes forget the old-school approaches to an agonizing problem.

With .htaccess, there isn't really anything external - a new point of failure - to screw up the redirects.

Re:Bit.ly was down by niggler on Sunday January 13, 2013 @12:42PM (#5051257)
>By sharing shortened links on twitter, you're not dealing with one man-in-the-middle, but two: Your own shortening service and Twitter's t.co shortener.

does Twitter shorten links that have already been shortened? Seems strange

Re:Bit.ly was down by jhund on Monday January 14, 2013 @12:51AM (#5053445)
Yes, as far as I can tell, twitter shortens every URL they encounter. I assume that they want their own share of the analytics cake.
Re:Bit.ly was down by bhaak on Sunday January 13, 2013 @08:39AM (#5050714)
Yes, indeed. Also, what about status pages that need javascript to work?