Danish Court Rules Deep Linking Illegal 382
Jstein writes "In a court ruling today Friday, the court in Copenhagen, Denmark ruled in favor of the Danish Newspaper Publisher's Association against the online news aggregator Newsbooster. Thereby deep linking has been ruled illegal for the first time." Currently the story is
only in Danish (from Computerworld Denmark, Online).
Update: 07/05 23:15 GMT by T : ttyp writes "Here is a link to an
English language story about the Danish deep linking case."
Deep linking? (Score:5, Insightful)
Also Illegal: (Score:5, Insightful)
- Citing specific pages in your footnotes.
- Pointing at specific locations with your finger.
Moronic. (Score:5, Insightful)
Of course you can use referrer technology to block how people get to your document, but these people seem to lack the ability to do things like that.
What if I bookmark a 'deep link'? What about Google?
Personally, I think that the term "deep link" is a misleading term - each document is equally accessible from outside, well except for a few bytes in the length of the URL.
Cheers,
Jim in Tokyo
New Meta Tag? (Score:4, Insightful)
I Corinthians 6:1
Dare any of you, having a matter against another, go to law before the unjust, and not before the saints?
Sensible in moderation (Score:5, Insightful)
However, it is well known that deep linking is good linking [useit.com] as far as users go.
I don't suppose there's any chance that publishers will come to a gentleman's agreement that it is improper to deep link if they explicitly ask not too (in the same way as it is considered "impolite" to provide direct links to files on others servers.
Finally, if DeCSS code can be considered "free speech", how can writing an URL not be subject to the same rational?
Goblin
Re:Hmmm. (Score:5, Insightful)
If you don't like this behavior, and you want "pages" on your site to only be accessible by people browsing through your site, you're going to need to stick a "document retrieval" application layer onto your site. Users start a session when they enter this application, and are only able to retrieve stories through this application front-end. This can be done through HTTP as simply as with a session ID, but the web was not meant to work like this.
Again, we have a rather useful technology being twisted and warped by corporate interests instead of those corporate interests funding a proper technological solution, just like the intellectual property crap associated with DNS nowadays.
Referer (Score:2, Insightful)
Re:Deep L:inking Defined (Score:2, Insightful)
Bookmarks also illegal? (Score:2, Insightful)
Re:New Meta Tag? (Score:4, Insightful)
Re:Hmmm. (Score:5, Insightful)
What's a "level"? If there is a specific, direct URL to a item, then it is already at the "top" level. That there are other ways to arrive at that URL is a conceptual design decsion, not a feature of hyperlinking or the Web itself. There is no "top" of a web site, other than mental contructs people impose on it, unless the web server enforces a particular sequence of URLs.
What's (almost) funny is that this is trivially easy to do, and just has to be cheaper than suing people, unless you are collecting damges each time.
It should be up to the web developer (Score:2, Insightful)
Re:Deep linking? (Score:3, Insightful)
Companies could prevent deep linking in a heartbeat just by redirecting anything that wasn't referred by their domain. That way people couldn't even send "deep links" to friends in e-mail...
It's a great way to have huge amounts of unaccessible information on a web page... Like phone trees, only more pathetic.
"'deep' linking" is a misleading term (Score:5, Insightful)
The reason "deep" linking should not be illegal is because there is no fundamental difference between a deep link and a regular link. We should quit playing the game by using this term to distinguish "deep" links from others.
You can't come up with a clear, unambiguous definition of deep links without having a special database or extension to the DNS database (!) to indicate what a site considers to be deep links on a case-by-case basis. In otherwords, the only clear and concise definition of a "deep" link is "a page on the website of Somebody Powerful that that Somebody doesn't want me to link to."
You can't just say, "A deep link is a link that goes somewhere besides the top of a site." For example, this [dallasnews.com] is a deep link (to a website that has tried to force people not to link to them, I might add), while this [geocities.com] is not. Both are links to something other than just ahost.domain.com, but the second is the top page of a site.
The real problem is web newbies (big media companies) think every website should have one entry point, but the web wasn't designed that way. We should quit helping these people persist in their misunderstanding of reality by using the term "deep link."
Don't even *use* the term "deep linking" (Score:5, Insightful)
Sorry to sound so RM-esque, but sometimes the words really *do* matter...
Re:Deep linking implications (Score:5, Insightful)
If the technology to prevent deep-linking is present, and a web-site that wishes to prevent deep-linking does not utilize (or attempt to utilize) this existing technology, they shouldn't be able to complain if someone deep-links to their site, IMNSHO.
Note that I am making two assumptions: implementing anti-deep-linking technology does not require the time or resources it would take to build a wall around 10 acres; the second is that you are just as able to give permission to deep-link as you are able to give permission for someone to murder you.
This case is about indexing, not deep linking (Score:5, Insightful)
What they're being sued over is having essentially copied the table-of-contents. They've taken the links and titles of all the newspaper articles directly from the webpage and presented them to users. Unlike
Under Danish copyright law, an index can be copyrighted. This copyright was violated.
This case sets no precedent for a site that collects links to articles about e.g. Linux, as such a site would have to put their own effort into making the index.
Everybody, STOP FSCKING PANICKING!
Thank you.
Re:Deep linking implications (Score:2, Insightful)
And I disagree with you as to why we abide "No Trespassing" signs. It's because I don't want to get my a$$ shot off by some looney character with a shotgun in his lap.
A better analogy might be the other way around... Take a look at research papers written MANY years ago. Take a look at their bibliography page. Is that not "deep-linking?" Thought so...
That's all we need is more frigg'n legislation to protect some ignorant people who are only comfortable if they're bitching about something. Face it, deep-linking has been around for years. It makes me so sick that these people (that are new to the Internet) think they own the damn thing. Christ, perhaps the elders of the 'net need to speak up. I know I've been on since it was commercialized mainstream around 1993/94 and frankly, I'm appauled as to where this is all heading.
Phil
Re:Deep linking? (Score:3, Insightful)
I haven't been a webmaster in a while, but I think the spread of smart browsers and privacy firewalls that supress "extraneous" information like Referrer: headers would make this unadvisable.
A Conversation (Score:2, Insightful)
husband: "oh, really? tell me more about it?"
wife: "well, they've got great food, authentic atmosphere, native Thai cooks & waitstaff"
husband: "wow, that sounds really great, can you tell me where it is?"
wife: "no, i can't. you see, Kansas City has this rule that you can't tell anybody how to get to where you really want to go, they want you to first go to Kansas City, drive around for a few hours, until you happen to see a road sign for your particular destination, and then you'll find out the location"
husband: "Wow, that's stupid!"
wife: "I know." ----EOF
Re:Deep linking implications (Score:3, Insightful)
It would be nice if technology was used to prevent this rather than court rulings, but hey, what can you do?
I am all for deep linking in most cases, and feel it should be legal. But I hate the idea that "there's a way to prevent it, so it shouldn't be ruled illegal." To me, that is the same as saying "There are ways to make your house burglar proof, so we shouldn't have to make breaking and entering illegal." Just because someone can prevent something from happening doesn't means they should have to prevent it. If we refuse to rule on things because there are ways to prevent it, what happens when those ways to prevent it are circumvented? Can we rule then? Or do we just wait for more ways to prevent the circumvention? I think deep linking is legal in most cases, but I want to see it remain legal because it is the right thing to do, not because there's a way to prevent it.
This whole "deep-linking" issue... (Score:2, Insightful)
It's funny how people have a tendency to take the law into their own hands the moment they think they have a handle on technology. I guess it's even funnier when judges go through with it.
Re:Deep linking implications (Score:2, Insightful)
No, it's not quite the same. If you want to make the analogy a little more reasonable, imagine that you installed a little electronic box on your door that, when someone walks up and says, "I want to go inside", unlocks and opens the door for them. This same box could be configured to only let in family members, but you decided that it would just be easier to sue your curious visitors for breaking and entering, then sue anyone who told them your address for aiding the crime.
If you want to make the analogy even closer, imagine that you live in a world where people enter others' houses this way, welcomed, billions of times a day, that they are unable to do anything but look around once inside, and that your only real complaint is that you wanted all your visitors to go to your neighbor's house and watch commercials first!
Finally, no, an HTTP request is not "circumvention" any more than saying "I want to go inside" is. If someone discovered that making the HTTP request 5 kilobytes long broke into the web server, or that shouting "MACKEREL!" at the top of your lungs broke the door opener, that would be clearly circumvention even though in each case you're just sending data or making noises. One set of data constitutes an understandable request (in the HTTP case, conforming to internationally recognized protocols); the other set is an intentional attempt to get in without making that request or having it answered.