News for hackers. Stuff that matters.
Re:Tr.im is now in the process of discontinuing service by pj on Sunday August 09, 2009 @06:51PM (#751428)
And the house of cards begins its collapse.

Let's hope it crumbles fast and we can rid the web of these shorteners before they cause more damage to the future of the internet.

Re:Tr.im is now in the process of discontinuing service by endtwist on Sunday August 09, 2009 @07:06PM (#751456)
One failure does not a trend make.

If another service flops in the next few months, then yes I agree, the house of cards is collapsing, but right now that statement is a little premature.

Re:Tr.im is now in the process of discontinuing service by tlrobinson on Sunday August 09, 2009 @07:12PM (#751474)
It's inevitable, whether it's in the next few months or in 5 years, we're going to end up with millions of broken links.
Re:Tr.im is now in the process of discontinuing service by iheartmemcache on Sunday August 09, 2009 @07:21PM (#751495)
Broken links have been happening since the web began. Any time you've made any web request, there's been a SPOF(1). In fact, think back to 2002-- remember when a good number of links you'd click were dead? When was the last time in recent memory you've had that happen? In fact, I argue that the web has a lower percentage of broken links today than back in the day. In 5 years, we'll likely have even less.

(1) Yeah yeah, I know, a drastic over simplification. There's Foundry LB hardware, round-robin DNS at different sites, BGP failover, etc.

Re:Tr.im is now in the process of discontinuing service by pj on Sunday August 09, 2009 @08:06PM (#751567)
broken links in the past were the result of actions of the creator of the content, however, in the case of url shorteners, the broken links are pointing to content that still exists, in the same place it was when the link was created.

There's a big difference betwen that an the broken links since the web began...

Re:Tr.im is now in the process of discontinuing service by mseebach on Monday August 10, 2009 @08:22AM (#752672)
> Any time you've made any web request, there's been a SPOF

And when you make a request through a shortener, there are two independent SPOF's.

Also, if you go to www.example.com/here/there/article and get a 404, you navigate up in the hierachy, and search for the content. If you get a 500 or server is down, you can try later. If either happens at the shortener-level, you're SOL.

Re:Tr.im is now in the process of discontinuing service by lyime on Sunday August 09, 2009 @08:02PM (#751561)
Sure, the percentage might decrease. But only because the number of total links are increasing by a ton.
Re:Tr.im is now in the process of discontinuing service by rjurney on Monday August 10, 2009 @07:56AM (#752620)
This is a problem google can solve pretty easily, isn't it? They've indexed both sides of the link... so they can somehow 'heal' the broken link - right?
Re:Tr.im is now in the process of discontinuing service by palish on Sunday August 09, 2009 @07:19PM (#751494)
Oh no!

... I'm sure we'll survive.

Re:Tr.im is now in the process of discontinuing service by joshu on Sunday August 09, 2009 @10:37PM (#751775)
Lots of these services are failing. I found a huge list of them once and MORE THAN A THIRD were marked as "defunct"
Re:Tr.im is now in the process of discontinuing service by ubernostrum on Sunday August 09, 2009 @07:17PM (#751492)
The argument against URL shorteners is specious, and taken to its logical conclusion is an argument against anyone ever linking to anything: any URL might turn up gone in the future, and you have no way of knowing or predicting which ones will last. Amazingly, the web's managed to survive this.

But if you're genuinely concerned that this poses some sort of threat to the web, start an archiving service which preserves mappings of short -> long URLs, or talk to the archive.org folks to see if they'd be interested.

Re:Tr.im is now in the process of discontinuing service by joshu on Sunday August 09, 2009 @08:45PM (#751623)
Straw man fallacy. A is like B and B is bad. Try again.

The argument is that it makes things MORE fragile, by interposing another party into the resolution chain. Given that it is both easy to do (thus there will be lots of competitors) and hard to profit at means that this party is more than usually vulnerable.

Anyway if the content dissapears, then it is gone. A url shortner failing means the failure could occur even if the content is still available.

Therefore, by definition, it is worse than the other situation.

Re:Tr.im is now in the process of discontinuing service by jimboyoungblood on Sunday August 09, 2009 @09:29PM (#751681)
You're presuming that URL shorteners don't provide any benefits that may justify the cost of a more fragile system. E.g., bit.ly gives you nice analytics, and many links are otherwise impossible to pass via Twitter.

Your argument against shorteners (extra indirection -> more fragile -> bad) works just as well against DNS. The reason why we tolerate the extra indirection of DNS is because there's a substantial benefit to be gained.

Re:Tr.im is now in the process of discontinuing service by Volt on Sunday August 09, 2009 @09:45PM (#751699)
DNS servers co-operate and the system has lots of built-in redundancy, whereas URL shortners have none of these properties. It's not just the indirection that makes them fragile.
Re:Tr.im is now in the process of discontinuing service by jimboyoungblood on Sunday August 09, 2009 @10:08PM (#751731)
So if there existed some sort of federated url shortening protocol, all the complaints about shorteners would go away?
Re:Tr.im is now in the process of discontinuing service by Volt on Sunday August 09, 2009 @10:35PM (#751769)
Probably not. The only place they're really warranted is on Twitter, so if Twitter did it themselves that would go a long way. There is the whole URL masking annoyance as well, so ideally Twitter would support long URLs, but that might not happen because of the 140 character SMS restriction.

A federated protocol seems a little much for this one service which can handle the issue themselves, IMO.

Re:Tr.im is now in the process of discontinuing service by jacquesm on Monday August 10, 2009 @03:01AM (#752125)
For plenty of fora they're handy as well, then there's IRC

Another good reason to have them is to be able to spell them for somebody over a phone line.

Re:Tr.im is now in the process of discontinuing service by anirbas on Monday August 10, 2009 @04:25AM (#752221)
I've also noticed a local free paper (Metro) using tinyurl links in its web section.
Re:Tr.im is now in the process of discontinuing service by bjelkeman-again on Monday August 10, 2009 @03:03AM (#752130)
Twitter should really, really provide a separate field for URLs. This would solve this whole thing.

What is the point of an SMS with a shortened URL if you have no internet access? To be able to access the web page you need web access. If you have web access then you can get at the longer URL in the web interface or via Twitteriffic etc.

Re:Tr.im is now in the process of discontinuing service by thwarted on Monday August 10, 2009 @02:41AM (#752100)
The inability to pass (some) links via twitter is the fault of twitter (or the "features" thereof), a fault that doesn't suddenly disappear because someone else provides what amounts to a workaround.
Re:Tr.im is now in the process of discontinuing service by PostOnce on Sunday August 09, 2009 @08:06PM (#751566)
That idea in the second paragraph of your comment is good. Someone ought to do that.

As far as the first, though, I think that you've got it wrong. It's not the same as any old site breaking. Say a person, over time, links to eight sites in his forum comments, and one goes down. Seven links are still valid. If he uses a shortener service that collapses, none of his links are valid.

Re:Tr.im is now in the process of discontinuing service by wave on Sunday August 09, 2009 @08:59PM (#751645)
Unshort.me is doing it. Look at the following post: http://news.ycombinator.com/item?id=577457
Re:Tr.im is now in the process of discontinuing service by nir on Sunday August 09, 2009 @09:41PM (#751695)
[Hi, Billy Mays here for..] TheRealUrl does it too, with JSON/P support and returning page titles as well! ;)

http://therealurl.appspot.com/

(it runs on Google App Engine, so I expect to keep it up as long as GAE exists. I didn't get TLD for it, to keep maintainance/costs at zero. And it memcaches everything, so feel free to query it as much as you like)

Re:Tr.im is now in the process of discontinuing service by tlrobinson on Sunday August 09, 2009 @10:36PM (#751772)
Re:Tr.im is now in the process of discontinuing service by nir on Sunday August 09, 2009 @11:20PM (#751846)
Nice one :) I was thinking of adding a downloadable list too - how did you get so many archived URLs? Do you have a cron running on Twitter/etc?
Re:Tr.im is now in the process of discontinuing service by ubernostrum on Sunday August 09, 2009 @08:20PM (#751594)
Say a person links to a series of articles, and the site which hosted them goes down. Now all the links are invalid, and this is nothing more than what we deal with every day.

The alarmist rants I've seen against URL shorteners are simply making this argument without realizing that there is no "new" problem in need of solving, only an old one that we already handle fairly well. Though given the level of irrational rhetoric I've been seeing in these discussions (example here: http://news.ycombinator.com/item?id=713998) I'm not sure there's any point trying to argue with it.

Re:Tr.im is now in the process of discontinuing service by judofyr on Sunday August 09, 2009 @08:46PM (#751626)
The problem with URL shorteners is that you now have two servers which can go down.
Re:Tr.im is now in the process of discontinuing service by tlrobinson on Sunday August 09, 2009 @10:40PM (#751778)
Not only that, but if it's an "original" URL that's broken but at least well formatted you at least have a hint of where to look, for example in the Google cache, archive.org, or elsewhere on the original domain.

Shortened URLs give you no hints as to where the original document was located.

Re:Tr.im is now in the process of discontinuing service by calambrac on Sunday August 09, 2009 @10:58PM (#751804)
Dude, you keep saying that "it's the same problem we've always had", but it simply isn't. You seem like a smart guy otherwise, so I don't know why you persist in making this assertion. The difference is simple: url shorteners introduce a middle man, another point of failure or abuse, and one that can't be fixed by the person who made the link (because they may forget the original target and not know who to contact) or the person who manages the target (because they can't set up a redirect from the old url).
Re:Tr.im is now in the process of discontinuing service by jacquesm on Monday August 10, 2009 @03:04AM (#752133)
Adding a link to a chain, any chain will make a it weaker:

Either the link is as strong as all the other links then you have a new element that can fail, which is bad, or your link is weaker than the other links in the existing chain and now the whole chain is weakened to the strength of the new link.

Re:Tr.im is now in the process of discontinuing service by webwright on Sunday August 09, 2009 @10:28PM (#751760)
No, it's really not.

Please explain why this (my last tweet):

"3x recommended dose of Vitamin D slashes cancer risk by 77%: http://is.gd/28Nbq

is better than this:

"3x recommended dose of Vitamin D slashes cancer risk by 77%: <a href="url">2005 Academic Study</a>"

I can see why you'd URL shorten when pushing to SMS, but an actual anchor/href gives me the ability to mouse-over and see the target URL and the link isn't dependent on a 3rd party to work. No one can frameset the url without the linkers permission or shove ads into the experience.

Re:Tr.im is now in the process of discontinuing service by mattmcknight on Sunday August 09, 2009 @10:45PM (#751791)
"There's a plugin for that." http://url.ly/app/tools [real URL!]

I find the shorteners an annoyance. You can't fix the dependency problem.

I wonder how they could increase SMS limits past 160 chars?

Re:Tr.im is now in the process of discontinuing service by a-priori on Monday August 10, 2009 @05:26AM (#752297)
I wonder how they could increase SMS limits past 160 chars?

That can't be done unless you change the underlying cellular protocol (e.g. the upcoming 3GPP LTE protocols). The length of an SMS is based on the capacity of one GSM frame.

Re:Tr.im is now in the process of discontinuing service by pvg on Sunday August 09, 2009 @09:33PM (#751683)
It's taken to a conclusion but not a logical one. A further conclusion based on that 'logic' would be that nothing at all should be made as anything might turn up gone in the future heat death of the universe.

Joshua Schachter has a nice summary of the arguments against that you may have seen before: http://joshua.schachter.org/2009/04/on-url-shorteners.html

Summary of the summary - URL shorteners have poor usability, providing little, often zero value at the cost of adding further centralized points of fragility.

Re:Tr.im is now in the process of discontinuing service by keyist on Sunday August 09, 2009 @08:20PM (#751595)
So let's promote the URL shorteners that are open and provided as free services, instead of those who try and sell click information.

http://ur1.ca is free software and provides a text format download of all its mappings right on its home page. Not a fan of shorteners, but that's the one I'd use for posting services with char length restrictions.

Re:Tr.im is now in the process of discontinuing service by robryan on Monday August 10, 2009 @02:10AM (#752076)
That was the problem they have had though, if they can't make any money then there is little point in their continued development work.
Re:Tr.im is now in the process of discontinuing service by jacquesm on Monday August 10, 2009 @03:05AM (#752134)
They can't make any money because it is not a unique proposition and it does not have any obvious hooks on how you could monetize it.

Conclusion, as an independent business it has very little chance of being viable.

Re:Tr.im is now in the process of discontinuing service by mynameishere on Sunday August 09, 2009 @08:35PM (#751615)
OTOH, they could be used as failsafes. If a normal link dies, tinyurl or whatever could go to a page that says,

"This link seems to be missing. Do you know where it moved to?" The responses could be published as long as the 404 continue. I have to think someone has already thought of this.

Re:Tr.im is now in the process of discontinuing service by martey on Sunday August 09, 2009 @09:33PM (#751684)
If the link is missing, the author/website admin should use a 301 code, not 404. See http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10...
Re:Tr.im is now in the process of discontinuing service by jacobolus on Sunday August 09, 2009 @09:53PM (#751710)
That doesn't work so well if the server/author/company goes away altogether.
Re:Tr.im is now in the process of discontinuing service by mynameishere on Sunday August 09, 2009 @10:12PM (#751735)
"should"