Dutch Court Says Linking Can Be A Form of Copyright Infringement
from the seems-a-bit-extreme dept
A somewhat troubling ruling has come out of a court in the Netherlands, where it has found that linking to infringing content could be infringing itself, if certain conditions are met (which they were in this case). The key part here was that the site that was sued was linking to material first, and thus revealing it to the world... even though it does not appear that the site in question uploaded or hosted the content. This is troubling for a variety of reasons which we'll get to, but first the background of the case.A Dutch television presenter, Britt Dekker, did a nude photoshoot for Playboy, and a bunch of the images leaked ahead of the December, 2011 release of the magazine. A website called GeenStijl.nl had a story about it, and included a link to a zip file that contained all the images that had been uploaded to the cyberlocker FileFactory.com. Playboy had the file taken down from FileFactory, and GeenStijl linked again to the same images on Imageshack. And from there a game of whac-a-mole followed with Playboy having the images taken down, but the images quickly spread all over the place. For what it's worth, at the time, there was a lot of speculation that Playboy itself had leaked the images to build up buzz.
Either way, GeenStijl got sued for copyright infringement -- and they responded by pointing out that they just linked to the content. The court put forth a three pronged test, and found that GeenStijl, even with just links, met the criteria for infringement. As explained on the FutureOfCopyright site (linked above):
The court considered if the publishing of the hyperlinks by GeenStijl.nl constituted a publication (Dutch: ‘openbaarmaking’) as defined in article 12 of the Dutch Copyright Act. In principle, placing a hyperlink on a website is not a publication, unless three criteria are met: there must be an intervention, a new audience and profit.By my reading, all three of the prongs of the test, as presented here, are somewhat problematic. The reasoning on the first prong -- intervention -- just doesn't seem right. The claim that "the public wouldn't have had access" but for the link on GeenStijl isn't true. They did have access since the files were already on the cyberlocker. GeenStijl perhaps made it a lot more widely known, but at this point you're arguing about whether or not it's legal to make a factual statement. Did the photos exist on a cyberlocker? Yes. Saying so shouldn't be infringing.
- Intervention: The leaked pictures of Britt Dekker were stored on FileFactory.com, a cloud service to store files and share them with others. However, these files can’t be found through search engines, only users with the exact URL have access to the files. The URL to the file with the leaked pictures was publicly unknown, until GeenStijl.nl made it available to its large audience by publishing an article about it, the court says. Therefore, the actions of GeenStijl.nl are an intervention, according to the court. Without this intervention, the public wouldn’t have had access to the pictures before their official publication in Playboy.
- New audience: According to the court, there wasn’t an audience for the pictures before GeenStijl.nl published its article.
- Profit: By publishing the URL to the pictures, GeenStijl.nl had the unmistakable intention to attract more visitors, the court states. With success: in 2011, the article about Dekker was the best viewed topic on GeenStijl.nl, according to the statistics.
The second prong really just seems like a repeat of the first prong. The entire argument that seems to have convinced the court is that GeenStijl was the first to link to the content. Under US law you face much more liability for leaking "pre-release" material, so you could argue that this is a similar situation in the Netherlands, but again, it's not GeenStijl "leaking" the material. They're acting as a journalist, telling people such content exists.
The final prong is completely useless. Basically it seems to say that because the article was popular, that's evidence for infringement. I can't see how that makes any sense at all. If GeenStijl was, for example, selling access to the images, then there's a much stronger argument of "profit." But just saying that because the site got a lot of traffic, they profited seems like a dangerous precedent.
The Future of Copyright article mentions the cases against FTD as being similar, but I'm not sure that's true. While a lower court had found FTD guilty for linking, on appeal it was said that links weren't the problem, it was the promoting of uploads that got FTD in trouble.
Either way, it's of little surprise that Tim Kuik, the head of the Dutch anti-piracy group BREIN, is cheering on this ruling, suggesting that this case will be useful in other efforts to go after sites that link to infringing content. Of course, given the specific nature of the ruling, including how much of it seemed to rely on the fact that GeenStijl was the first to somehow create an audience for these images, I do wonder if it really has that much value for BREIN in those types of cases. Similarly, it may be a bit exaggerated to claim -- as GeenStijl did in response to the ruling -- that the ruling outlaws Google. Again, the ruling does appear to be highly fact-specific.
It is a troubling ruling for a number of reasons. Merely setting up the precedent that a link itself is infringement has all sorts of problematic implications. But the highly specific details associated with the ruling, especially the reliance on being the first to publish the link, at least suggests that this has limited value as a wider precedent.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: copyright, infringement, linking, netherlands, playboy, tim kuik
Companies: brein, geenstijl, playboy
Reader Comments
Subscribe: RSS
View by: Time | Thread
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Ignoring precedent doesn't make it go away. When someone knowingly links to an infringing file, it is for the purpose of facilitating infringement. It should come as no surprise that the law actually holds people responsible for the infringement they intend to facilitate.
[ link to this | view in chronology ]
Re:
someone else was holding them.
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
[ link to this | view in chronology ]
Re: Re:
Mike has made clear many times that he doesn't think linking should give rise to any liability. And usually he makes the "but if linking is infringement then Google is an infringer!" argument. This, of course, ignores the fact that there has to be intent. And it ignores the fact that Google can be an infringer for linking.
Google search's automated organizing of the web isn't infringement because there's no knowledge of linking to any specific infringing file. But once Google is given notice that a link points to an infringing file via a DMCA takedown notification or some other method, Google removes the link. Why? For the reasons mentioned by the Ninth Circuit. Once Google has knowledge that a specific link points to infringing material, Google is thereafter facing liability for whatever infringement occurs via that link. The intent to cause that infringement is imputed.
Mike sticks his fingers in his ears and pretends like linking creates no liability. The truth is that sometimes it does, and sometimes it doesn't. And don't be confused by the fact that the liability is for contributory infringement. Contributory infringers are still susceptible to the full range of remedies provided by the Copyright Act which include money damages and injunctive relief. A contributory infringer is an "infringer" under Section 501, and they are treated the same as a primary infringer.
[ link to this | view in chronology ]
Re: Re: Re:
We know.
This, of course, ignores the fact that there has to be intent.
So, you think that copyrighted images should be off limits, even in the situation of the press? Tell, oh, every source of the news that's ever existed, because this is no different. A blog that says "Hey, someone leaked these photos! See? We're not lying, here's a link. (link)" isn't guilty of copyright infringement. Hint: think of how this could easily be used to stifle free speech, if you're weren't wrong.
Google blah blah blah Google, links, Google.
Google is a search engine, not a blog. In related news, oranges aren't apples.
Ad Hom, baseless statement, baseless statement, scary words, scary words.
If the "threats" of Section 501 were worth anything, we wouldn't be here discussing this, because copyright infringement would be no more. No one cares.
[ link to this | view in chronology ]
Re: Re: Re: Re:
Say there's a copyrighted video that I want to help others infringe upon, and I provide a link: http://www.pirateapologists.com/mikeblowsyoungboys.avi
By providing the link, I'm facilitating the infringement that occurs when people click on it. Under these facts, I'd be a contributory infringer.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
This is the crux of your argument, and, it so happens, where it fails. How do you differentiate between a blog merely informing people that a noteworthy copyrighted work is leaked, versus that they wanted to "help others infringe"?
Further, if you actually think about the actions monopolized by copyright, which one was violated? No copy was made by a link. It's just a pointer to a location; an address.
In the end, though, people really don't care about copyright, and it's people like you that were the cause; just ask Newton.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re:
The part that I said is well-settled is that one who authorizes an infringement without the authority to do so is a secondary infringer because they are violating the right holder's exclusive right "to authorize" that activity. Whether or not a linker is an authorizer is not well-settled, as you point out, but that's not the point I made. I believe that linking to an infringing can lead to liability, not that it necessarily does. It depends on the facts, as I've indicated several time.
I said: "A linker is authorizing copying when they don't have the right to do so." I believe that to be true, and it follows from the Ninth Circuit case I quoted that you don't appear to understand. See http://www.techdirt.com/articles/20120914/05442020382/dutch-court-says-linking-can-be-form-copyright -infringement.shtml#c770
I then said: "It is well-settled that one who authorizes copying when they don't have the right is a contributory or vicarious infringer." That is well-settled, as I'm sure you know. So, no, I don't agree that I said anything wrong.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
I don't think I misrepresented anything. What I said is true. A linker is an authorizer (true; but unsettled), and it is settled that an authorizer is a contributory infringer (also true). I'm simply making an argument--one that the Ninth Circuit had no trouble making. I even cited precedent and everything.
So I said X implies Y (which I did not say was settled), and then I said Y implies Z (which I said is settled). You mistook what I said to imply that X implies Z is settled. I didn't say that. That you made a mistake does not mean I'm being "weaselly."
You're really going to great lengths with this. Silly.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
http://www.pirateapologists.com/mikeblowsyoungboys.avi
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
pirateapologists.com/mikeblowsyoungboys.avi
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
The First Amendment argument isn't going to win since it's the functional aspect of the link that's at issue, not the speech aspect. You can get heightened First Amendment scrutiny perhaps, but as the Second Circuit held, a copyright law will pass such scrutiny. The link isn't removed because of the speech aspect. It's removed because it's being used to cause infringement.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
What if I told you that my web browser lets me select text, right-click on it, and, if the text is a valid URL, open it in a new tab? Is that illegal for browsers to do, because it can facilitate copyright infringement?
[ link to this | view in chronology ]
Re: Re: Re:
The truth is that sometimes it does, and sometimes it doesn't.
I think the only way would be for the news outfit to upload the pictures themselves. Did that happen?
And don't be confused by the fact that the liability is for contributory infringement.
Did they upload the material?
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re:
I'm responding to that statement. You're the one derailing things.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Google
There is a concerted effort to 'ripen the minds' as to force Google not to index an immense part of the web. Will it work? Probably.
[ link to this | view in chronology ]
Re: Google
[ link to this | view in chronology ]
Re: Re: Google
[ link to this | view in chronology ]
Re: Re: Re: Google
[ link to this | view in chronology ]
Re: Re: Re: Re: Google
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Google
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
By that reasoning,
Calling to report a bank robbery is the same as robbing a bank.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
"Sure, he lives down at the corner of XX street and YY avenue."
"Thanks."
Oh, and it turns out that Mr. Big is a crime boss, but whether or not I knew that doesn't matter, I just pointed someone out to where Mr. Big is.
Now, does that make me guilty of, let's say a shoot out that happens where Mr. Big is?
I obviously pointed out where he is, so I facilitated a crime.
But, if I'm not guilty of that, then why is a person who links to something guilty?
And, please, no appeals to authority, emotion, ETC, joe.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
He's definitely a constructive fellow.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
It's is a very worrying judgement, among other targetting comment pages.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re:
Yes, they want to keep the safe harbor. The safe harbor is irrelevant the ultimate issue of liability, but it certainly drastically reduces the liability they might face if they are in fact liable. But the same inaction that could cause them to lose the safe harbor, namely, not responding to a DMCA takedown notification, could also subject them to contributory liability for the links they failed to take down. The safe harbors are basically (but not completely) just codifications of common law principles. Even if Google didn't qualify for the safe harbors, I don't see how Google could be liable for the links it provides absent specific knowledge that they point to infringing material.
I'd look to cases like this one: Field v. Google Inc., 412 F. Supp. 2d 1106, 1116 (D. Nev. 2006).
There's other arguments too, like fair use, but I don't have time to dig that up right now.
[ link to this | view in chronology ]
Re: Re: Re:
You are, once again, lying. I've never seen Mike say that links should never give rise to any liability.
He has said that linking should not be an infringement in and of itself. And the courts agree - including the case you just mentioned:
This is relevant to the seizures, which are criminal cases, because there is no "secondary liability" in the criminal statutes. But that's not saying, and Mike never said, that there should be no liability at all.
I'm really getting sick of you lying, Joe. For a while, it was interesting debating the law with you. Now I realize you're just spouting off off-topic legal quotes to smear Techdirt. It's really sad.
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re:
The post I'm thinking of was just last month where Mike, when talking about "websites that involve either links or embeds of videos hosted elsewhere," pondered, "how is such a site infringing at all?"
Link: http://www.techdirt.com/articles/20120803/05165019928/judge-posner-embedding-infringing-videos-is-no t-copyright-infringement-neither-is-watching-them.shtml
So right there it's pretty clear that he doesn't see how linking and embedding can possibly be infringing. Towards the end of the article he states that "hosting the embed code" is not infringing. And he concludes that the infringement is "completely disconnected from the . . . the site doing the embedding." Of course, Mike was completely misreading the opinion out the Seventh Circuit. My opinion is that he did so intentionally, but that's neither here nor there.
So clearly I'm not lying, and Mike has explicitly claimed that links aren't infringing. Strike 1.
He has said that linking should not be an infringement in and of itself. And the courts agree - including the case you just mentioned: The Ninth Circuit there was discussing direct liability for infringement of the display right. The clue is that it comes under the section heading "III. Direct Infringement A. Display Right." The court said that linking is not direct infringement. I never claimed otherwise (although I do disagree with the Ninth Circuit on that point, and there is some caselaw and commentary that suggests otherwise).
You need to read the part of the opinion that comes later (under the helpful section heading "IV Secondary Liability for Copyright Infringement A. Contributory Infringement") where the court of appeals says that linking can give rise to indirect liability for infringement.
Given that the issue is contributory infringement, there has to be primary infringement, so in that sense linking "in and of itself" is not infringement. You could say that about all contributory infringers. But I never claimed otherwise. Nor do I believe Mike has ever made that distinction (he's too busy pretending like linking gives rise to no liability). So no, I don't get your point. Strike 2.
This is relevant to the seizures, which are criminal cases, because there is no "secondary liability" in the criminal statutes. But that's not saying, and Mike never said, that there should be no liability at all.
The Copyright Act doesn't distinguish between direct and indirect infringers, and both are treated the same under Section 506. So you're wrong. Section 506 creates criminal liability for infringers, whether direct or indirect.
And Mike did question how linking sites are "infringing at all," so you're wrong there too. Strike 3.
I'm really getting sick of you lying, Joe. For a while, it was interesting debating the law with you. Now I realize you're just spouting off off-topic legal quotes to smear Techdirt. It's really sad.
Huh? No matter, 'cause... You're out! ;)
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
In that article, he is asking how those particular sites - which did not host or store any materials themselves, and whose links were put there by users, not site owners - could be held liable for any form of infringement.
Given the myVidster ruling - which held that myVidster is not even liable for contributory infringement - it's a very good question.
But it does not mean that a site that provides links can never be liable for contributory infringement. Just that it must be shown that they must do more than merely provide links to infringing material.
Strike one.
You need to read the part of the opinion that comes later (under the helpful section heading "IV Secondary Liability for Copyright Infringement A. Contributory Infringement") where the court of appeals says that linking can give rise to indirect liability for infringement.
I have. But "contributory infringement" is not actually infringement. It can give rise to civil liability for contributing to someone else's infringement, but it is not in itself infringement.
A link site may be held liable for contributing to the infringement, if the site hosting the links is "intentionally inducing or encouraging direct infringement." That is, if the site hosting the link intentionally induced or encouraged users to upload infringing material to third-party hosting sites, it can be held liable for those users' infringements. But merely providing a link to already-existing material does not, by itself, do this.
And, yes, Mike made the distinction: "After all, the videos themselves were uploaded by other people to other sites. The streaming occurs from those other servers. The embed just points people to where the content is, but it does that neutrally, no matter what the content might be."
You may disagree with him that providing links does not "intentionally induce or encourage" the users to upload videos to the third-party sites. (You would be wrong, but you could disagree.) What you cannot claim is that Mike said no liability whatsoever could ever possibly arise from any linking sites. That would be an outright lie.
Strike two.
The Copyright Act doesn't distinguish between direct and indirect infringers, and both are treated the same under Section 506.
This is complete and utter bullshit. If the statutes didn't distinquish between "direct" and "indirect" infringers, then both would be "direct infringers" under the statute. Either you infringe on the rights granted in 17 USC 106, or you don't. If you don't, then you're not an infringer.
Civil law can hold some people liable for the infringement of others, under theories of "contributory" or "vicarious" infringement. But that liability does not arise from copyright statutes, but from "rules of fault-based liability derived from the common law." As Judge Posner observed in the myVidster ruling:
This is so universally accepted, that I'm surprised you even bring it up. If you believe it, then you're even more ignorant of the law than I am.
But I don't believe you are. Which means that you're simply being misleading. Again.
Strike three.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
That's not true. He never says that he's only discussing sites where the links are provided by third-parties. He says, "the videos themselves were uploaded by other people to other sites," but he does not say that the links were also provided by others. Nor would it matter whether the links were provided by others. If the site owner encouraged others to post infringing links, or if the site owner received notification (and thus knowledge) that infringing links were there, the site owner could still be liable. The fact that others post the links doesn't mean that the site owner can't be liable for them. So I don't get your point.
Given the myVidster ruling - which held that myVidster is not even liable for contributory infringement - it's a very good question.
In that particular case on that particular record, myVidster wasn't liable. But nowhere in the opinion does the court of appeals say that a linking site can never be liable. Quite the opposite, in fact. See, e.g., http://tmtlaw.default.wp1.lexblog.com/2012/08/15/did-the-flava-works-decision-create-a-copyright-loo phole-for-online-video/ Posner said myVidster wasn't liable for the embeds because there was no admissible evidence that anyone used them to watch infringing videos. Change the facts and the outcome could change too. Linking sites can be liable.
But it does not mean that a site that provides links can never be liable for contributory infringement. Just that it must be shown that they must do more than merely provide links to infringing material.
Again, that doesn't contradict anything I said. Nor did Mike ever make the distinction that you're pretending he made. Mike didn't say, "Well, linking can lead to liability if other facts are present." He questioned whether it could ever lead to liability: "how is such a site infringing at all?" Nice try at revising, but no dice.
I have. But "contributory infringement" is not actually infringement. It can give rise to civil liability for contributing to someone else's infringement, but it is not in itself infringement.
Huh? That makes no sense. A contributory infringer is an infringer. Contributory infringement is actually infringement. The Supreme Court has referred to "the fact that an infringer is not merely one who uses a work without authorization by the copyright owner, but also one who authorizes the use of a copyrighted work without actual authority from the copyright owner." Sony v. Universal, 464 U.S. 417, 435, n.17 (1984). If you read Section 106, you'll notice that copyright owners have the right "to do and to authorize" the given acts. One who authorizes an infringement is an infringer. It's called "contributory infringement" because it is in fact infringement.
Here's the Ninth Circuit discussing contributory infringement: Perfect 10 v. Visa, 494 F.3d 788, 794-95 (9th Cir. 2007).
If you look at Section 501, it states: "Anyone who violates any of the exclusive rights of the copyright owner as provided by sections 106 through 122 . . . .is an infringer of the copyright." Those rights include the right to do and to authorize an infringement. One who contributes to the infringement of another is himself an infringer. This follows from the source of contributory infringement, which is the tort doctrine of enterprise liability. Contributory infringers are jointly and severally liable with the primary infringers. They are both infringers, liable for the same infringement. The law considers them to have acted together to cause the same infringement.
A link site may be held liable for contributing to the infringement, if the site hosting the links is "intentionally inducing or encouraging direct infringement." That is, if the site hosting the link intentionally induced or encouraged users to upload infringing material to third-party hosting sites, it can be held liable for those users' infringements. But merely providing a link to already-existing material does not, by itself, do this.
That's not what the Ninth Circuit said in Perfect 10 v. Amazon.com, which I quoted at length. It matters not whether the linker or site hosting the links played a part in uploading the infringing file. The court of appeals said that Google could be liable for failing to remove a link to infringing material. There was no condition that Google had to have played a part in that material being uploaded to a third-party site in the first place. Nor does that make any sense. The court makes clear that the link itself materially contributes to the underlying infringement without the need to show that the site played a role in placing the infringing material on other sites. If the site played such a role, that could lead to liability as well.
And, yes, Mike made the distinction: "After all, the videos themselves were uploaded by other people to other sites. The streaming occurs from those other servers. The embed just points people to where the content is, but it does that neutrally, no matter what the content might be."
That "neutrally" claim made me laugh. That's like saying the bullet that came out of my gun and into your head flew there "neutrally." It ignores the fact that I pointed the gun at your head in the first place. Moreover, that quote only shows that Mike was making a distinction about who put the files on the third-party sites to begin with. That mentions nothing about the links, nor does your new argument (one that Mike did not make) that the linker must also have played a role in the uploading of the linked-to file hold water. The Ninth Circuit found that Google could be liable for the link without reference to Google's role in the uploading of the linked-to file.
You may disagree with him that providing links does not "intentionally induce or encourage" the users to upload videos to the third-party sites. (You would be wrong, but you could disagree.) What you cannot claim is that Mike said no liability whatsoever could ever possibly arise from any linking sites. That would be an outright lie.
I don't disagree that subsequently linking to a file that someone else already uploaded doesn't encourage that person to commit an act that they already have committed. That makes no sense. About a linking site, Mike questioned "how is such a site infringing at all?" It is not a lie for me to say that Mike doesn't think that links should give rise to liability when he explicitly questioned such a thing.
This is complete and utter bullshit. If the statutes didn't distinquish between "direct" and "indirect" infringers, then both would be "direct infringers" under the statute. Either you infringe on the rights granted in 17 USC 106, or you don't. If you don't, then you're not an infringer.
Contributory infringers are jointly and severally liable with the primary infringers they aided. I'm not saying that both direct and indirect infringers are direct infringers. I'm saying that under the Act, both are infringers. A contributory infringer is an infringer, as I've pointed out. The Act treats both the same in that both are jointly and severally liable for a given act of infringement. Both the primary and the secondary infringers are liable together for the infringing act they both worked together to bring about.
Civil law can hold some people liable for the infringement of others, under theories of "contributory" or "vicarious" infringement. But that liability does not arise from copyright statutes, but from "rules of fault-based liability derived from the common law." As Judge Posner observed in the myVidster ruling:
The law doesn't recognize "secondary infringement" either. The only distinctions relevant to this case are between direct infringement (which really ought just to be called infringement) and contributory infringement, and between contributory infringement and noninfringement. The direct infringers in this case are the uploaders.
Right there Posner says that there is "contributory infringement," which just above you said doesn't exist. And you're pulling that quote from the Ninth Circuit out of context. The court of appeals said: Perfect 10 v. Amazon.com, 508 F.3d 1146, 1170-71 (9th Cir. 2007).
So the court of appeals did not say "that liability does not arise from copyright statutes," they said that liability is to be examined under the tort concepts from which it arose such as enterprise liability. This includes the concept that secondary tortfeasors are jointly and severally liable with the primary tortfeasors they assist. Both are liable together for the single infringement.
This is so universally accepted, that I'm surprised you even bring it up. If you believe it, then you're even more ignorant of the law than I am. But I don't believe you are. Which means that you're simply being misleading. Again.
So because you misunderstand the law, I'm ignorant? I don't see it. I don't lie. I may get stuff wrong, but I try very hard to back up everything I say and to be careful with my words. I hate getting stuff wrong.
One thing I think you're missing from Flava Works is that Posner said that they couldn't be liable for contributory infringement for embedding links to infringing videos hosted elsewhere because there was no evidence that anyone clicked on any of the links: "In contrast, Flava's pirated videos are not sold, and there isn't even admissible evidence that they're actually being accessed via myVidster, rather than via other websites, and if they are not, myVidster is not contributing to their performance." Perhaps once discovery is complete (the motion for a preliminary injunction was filed well before discovery concluded) it'll be a different story.
And another thing you're missing is the import of the right "to authorize" in Section 106. While the Supreme Court in Sony said that contributory infringement is not explicitly mentioned the Act, the right "to authorize" in fact is an explicit mention of contributory infringement. As Patry explains in his treatise: 6 Patry on Copyright § 21:43.
The legislative history is clear that the right "to authorize" was meant to cover contributory infringement. Other courts have picked up on this, but there is definitely some confusion on the point caused by the Supreme Court's careless statement to the contrary.
Have a good weekend, Karl. I won't have time for another lengthy response today.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
And neither did Mike. He said a link can never be infringement. He's right.
Huh? That makes no sense. A contributory infringer is an infringer.
This is wrong. A contributory infringer is one who contributes to the infringement of another. They need not, themselves, actually infringe anyone's copyright to be considered liable.
And it is indeed a big difference, because the quote from Mike was specifically about the myVidster case. That case was significant because the MPAA had claimed that linking or embedding is direct infringement. The exact quote: "myVidster users who posted embedded links to video streams directly infringed the performance right even though they did not necessarily possess a copy of the infringed work."
As it turns out, the MPAA was wrong. Big surprise there.
Sony v. Universal, 464 U.S. 417, 435, n.17 (1984).
Here's another direct quote from Sony: "The Copyright Act does not expressly render anyone liable for infringement committed by another. [...] The absence of such express language in the copyright statute does not preclude the imposition of liability for copyright infringements on certain parties who have not themselves engaged in the infringing activity."
And half of the passage you quoted explained exactly how secondary infringement is not in the copyright satute, but arose solely from civil case law. "Contributory copyright infringement is a form of secondary liability with roots in the tort-law concepts of enterprise liability and imputed intent." "In Metro-Goldwyn-Mayer Studios, Inc. v. Grokster, Ltd., the Supreme Court adopted from patent law the concept of 'inducement.'" And so on.
It's really amazing that the very case you quote explains how you're wrong.
In civil cases, it doesn't make that much difference. But in criminal cases, it does. Criminal cases cannot go beyond the "express language in the copyright statute." They cannot use the contributory infringement standards from Napster, Grokster, etc, because those standards did not arise from the copyright statute - as the court in Sony made explicitly clear.
As Patry explains in his treatise:
Patry is right in one sense - the "to authorize" phrase is designed to punish contributory infringers. It does this by making them no longer contributory infringers, but direct infringers.
Of course, "authorized" is a very strong word - for example, Napster or Grokster didn't "authorize" the use of any copyrighted materials. They materially contributed to others' infringements; they induced infringement by others. But the doctrine of contributory infringement that was created under Napster, Grokster, etc., had absolutely nothing to do with "authorizing." As the text of the cases themselves make absolutely clear, those cases created their versions of secondary liability directly from civil case law, not 17 USC.
As an aside - here's a phrase by Patry that I really love:
That's not what the Ninth Circuit said in Perfect 10 v. Amazon.com, which I quoted at length.
Sorry. The Techdirt link you pointed me to was about myVidster, which was a streaming case. In that case, the link site would have to induce or encourage direct infringement, because viewing an unauthorized performance in private is not an infringing act. Even if the link site actively encouraged people to watch those streams, they would not be liable for infringement. At least according to Judge Posner.
So, in that particular case, the linking site would have to directly assist or encourage the uploaders, since they are the only ones who are directly infringing. And it was absolutely apropos to the website seizures, since the majority of them are streaming cases (amazingly enough).
The Perfect 10 case dealt with users who were downloading (i.e. copying) images to their computers, which is an infringement in and of itself, so the above doesn't apply. And, yes, in that particular case, Google could be liable for contributory infringement (but not direct infringement, inducement, or vicarious infringement) if they "knowingly takes steps that are substantially certain to result in such direct infringement."
However, merely providing a link does not impute such knowledge; they must have "actual knowledge that specific infringing material is available using its system" (emphasis in original).
Right there Posner says that there is "contributory infringement," which just above you said doesn't exist.
See? Lying again. I never said that contributory infringement doesn't exist. I said that it is the application of liability to people who do not themselves infringe. And I am right.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re:
Do you agree that under the Ninth Circuit's reasoning in Perfect 10 v. Amazon.com, a party that knowingly links to an infringing file can be liable as a contributory infringer for whatever infringement takes place by others who use that link?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
Interesting demand, seeing as you are not even capable of reigning in your compulsive hatred of Techdirt, and the insults and borderline slander that go along with it.
But, sure, I'll go with it.
Do you agree that under the Ninth Circuit's reasoning in Perfect 10 v. Amazon.com, a party that knowingly links to an infringing file can be liable as a contributory infringer for whatever infringement takes place by others who use that link?
"Can be?" Sure. "Is necessarily?" No.
[ link to this | view in chronology ]
Re:
In any case, besides all you annoying square and limited view of the world where "the law is the law" I do agree, partially, that the news outfit kept putting the images on. However there are a few points that should be addressed before pointing fingers:
1- They are reporting. Reporting. So they just updated the links where the material was available as it was part of the article.
2- The material is already public anyway. You can't take back what has already spread to the public. If you tell your password out loud people will remember it regardless of you shouting for them to forget. So there's little point in trying to censor anything over it. The Internet has a memory. And it has Barbra Streisand.
3- Of course none of that matters in face of the law but it's pretty clear they DID NOT leak (prong number 1 down), they just reported about something that was already on the Internet (prong number 2 down) and didn't profit on the works of Playboy but rather in the service provided (news.. and prong 3 is down).
So unless you are admitting that the law can be interpreted in multiple ways, all your previous whining that "the law is the law" is invalidated since you are conceding the law can have interpretations based on each different case.
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
So, you think that copyrighted images should be off limits, even in the situation of the press? Tell, oh, every source of the news that's ever existed, because this is no different. A blog that says "Hey, someone leaked these photos! See? We're not lying, here's a link. (link)" isn't guilty of copyright infringement. Hint: think of how this could easily be used to stifle free speech, if you're weren't wrong.
They should NOT be liable for reporting.
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
Honestly I don't see how linking to anything could be consider infringing. I agree with the AC above you: It isn't and shouldn't be. It's just a link. What is the harm in clicking on something that could be useful in getting something done?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
I feel like that every time that you reply, I'm going to repeat this to you: "It's just a link. I shouldn't worry about it."
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
Isn't it amusing that you say these things, which are insulting and based on no actual facts yet you're the first to cry foul over being insulted?
Perhaps you should change your username to average_hypocrite
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
I don't care if he holds different values. The world would be a boring place if everyone thought the same things I think. I care that he's arrogant and deceitful. Those are personality flaws that he should work on. I'm attacking his credibility because I find he has none. After years of reading this blog and trying to engage him myself and watching others try, I've come to the inescapable conclusion that he's just a zealot who doesn't ever want to be challenged. He'll go on spouting his nonsense no matter how much evidence is stacked against him. He only cares about spreading his agenda, not in seeking out the truth.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
I don't just assume bad faith. After two and a half years of reading this blog and watching Mike be weaselly (nice word, thanks) and arrogant and all the other nasty things I've witnessed, I've deduced bad faith. There is no other explanation.
I didn't say I'm not here to second guess people's motives or beliefs. I'm OK with a myriad of beliefs, and I have no problem being challenged on mine (as you're doing) or challenging others. It's when bad faith enters the picture that I get upset. And I think Mike runs in "bad faith" mode 24/7.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
Now we know how hard you have been in your interpretations of law to always cast them on the maximalist side.
You clearly all these years have not been an interested law student, but a lobbyist for the legacy content industries.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
The two are in conflict, that much is clear. I don't agree that it's all-or-nothing as you do. I think a balance is possible and preferable. You think in extremes. I don't.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
So basically, until you start thinking outside the box with your comments, no one will take you seriously.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
So basically, until you start thinking outside the box with your comments, no one will take you seriously.
What the law says is a different issue than whether it's just. Mike starts with his conclusion, which is usually an extremist position on what's just, and then works backward to make the law fit that conclusion. So with linking, he doesn't think policy-wise that it should lead to liability. So when he looks at the law, what does he see? No liability. I prefer to look at the what the law actually says and to discuss what is the better policy separately.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
That's the groove of a lot of these opinion blog posts. The whole point is to discuss whether it's just or not, not make assumptions about the author's ideology.
This is a perfect example in your first post:
"I know you don't like to acknowledge this, but intentionally linking to infringing content can create copyright liability."
This is the entire basis for your posting here, to prove that Mike doesn't like to acknowledge that linking content can create copyright liability.
It's common sense or at least should be that linking can create copyright liability, and I doubt Mike would argue about that, but saying this gives you a reason to start picking a fight instead of contributing to some kind of meaningful discussion.
There's better ways to express dissent.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Similar to the English law
- induced, incited or persuaded the users to infringe, and
- acted with the users "pursuant to a common design to infringe".
That seems to be similar to the first paragraph quoted above. Additionally, the court also found them liable for "authorising" the infringing acts of the site's users (authorisation of infringement is an infringement itself under English law), in which case they looked at:
- The convenience of the means of infringing,
- Inevitability of infringement (not just inevitable, but intended),
- Degree of control (i.e. operators did remove some links),
- Steps to prevent infringement (i.e. none).
Again, similar patterns emerging. As far as "actual knowledge" of specific infringements goes, that is the sort of language used in the E-Commerce Directive - which will also apply in the Dutch case.
Anyway, back to the underlying principle of liability for linking; I think the mistake many people make (including, perhaps, Mike) when it comes to copyright and the Internet is that they think that the precise technology, and the precise location of the data etc. matter. They don't. The law talks about infringements; in EU law that includes "communicating to the public", which is intentionally broad enough to cover all sorts of things.
But again, that is missing the point. This (and stuff about linking) isn't about primary liability, but secondary or joint liability, which are pretty entrenched concepts in common law jurisdictions; if you're sufficiently involved in someone else's tort, you may be liable for it yourself. I haven't read the Dutch court judgment, but the principle seems to be that if you are knowingly and deliberately inciting other people to break the law (especially doing so for personal profit), you should be liable for doing so, whether or not you did the actual primary infringement.
[ link to this | view in chronology ]
Re: Similar to the English law
Consider this: You post is copyrighted.
How about I post a link to it saying "Hey, this is a great post that I didn't wright. Check it out."
Don't know who owns the copyright, but by this interpretation, I'm pretty sure I've just violated it.
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
That's not so.
The very first sentence of the opinion: "In this appeal, we consider a copyright owner's efforts to stop an Internet search engine from facilitating access to infringing images." 508 F.3d 1154. The issue is Google's search engine, specifically its image search which links to infringing images.
The court said several things:
I. Direct Infringement; 508 F.3d at 1159-68.
(1) Applying the server test, the court found that Google didn't directly violate the display right for inline linking to full size images hosted elsewhere.
(2) Using similar reasoning, the court also found that Google didn't directly violate the distribution right by inline linking to full size images hosted elsewhere.
(3) As to thumbnails, the court found that Perfect 10 had made out a prima facie case of direct infringement of the display right. However, the use was fair so there no liability on Google's part.
There was a similar ruling as to the cache that I'm skipping.
II. Indirect Infringement; 508 F.3d at 1168-75.
(4) The court found that Google could be liable for contributory infringement for failing to remove links when notified that they pointed to infringing material.
(5) The court found that Google wouldn't be liable for vicarious infringement since they didn't have the right and ability to control the direct infringers.
******
Here's the text that shows I'm right.
Right after the section heading "Secondary Liability for Copyright Infringement," the court states: "We now turn to the district court's ruling that Google is unlikely to be secondarily liable for its in-line linking to infringing full-size images under the doctrines of contributory and vicarious infringement." 508 F.3d at 1168-69. The issue was whether Google was "secondarily liable in light of the direct infringement that is undisputed by the parties: third-party websites' reproducing, displaying, and distributing unauthorized copies of Perfect 10's images on the Internet." 508 F.3d at 1170.
So the court is explicitly talking about secondary liability for inline linking to infringing images hosted on third-party websites.
Look at the section labelled "A. Contributory Infringement." That entire section is about whether Google is contibutorily liable for infringement for inline linking to images hosted on third-party websites.
The court concludes by stating: "Applying our test, Google could be held contributorily liable if it had knowledge that infringing Perfect 10 images were available using its search engine, could take simple measures to prevent further damage to Perfect 10's copyrighted works, and failed to take such steps." 508 F.3d at 1172. So by knowingly providing links to infringing images in its search results, Google is facing contributory liability. The way Google makes Perfect 10's images available via its search engine is by LINKS. That's the whole point.
There was a factual dispute that needed to be resolved, so the case was remanded: "Therefore, we must remand this claim to the district court for further consideration whether Perfect 10 would likely succeed in establishing that Google was contributorily liable for in-line linking to full-size infringing images under the test enunciated today." 508 F.3d at 1173. It couldn't be any clearer than that.
So, no, I don't agree with you. The issue was inline linking, not hyperlinking, but I don't see how that could possibly make any difference. Either type of linking could lead to contributory liability under the court's logic.
[ link to this | view in chronology ]
Re: Re: Re:
"The court found that Google could be liable for contributory infringement for failing to remove links when notified that they pointed to infringing material. "
but this:
"but intentionally linking to infringing content can create copyright liability"
is not an accurate restatement of that opinion and therein lies the problem. The court didn't find that linking is contributory infringement it found that failing to remove the links after being notified they were to infringing material could be contributory infringement. You're essentially trying to conflate the 'knowledge' being refereed to in the ruling, being actual legal knowledge as a result of direct notification, with 'common sense' or general knowledge, which is really nothing more than an educated guess or suspicion. Again, nowhere in that ruling, even the sections you've quoted, does it talk about links themselves constituting infringement it takes about lack of action after having knowledge opening the possibility of contributory infringement. It's like you're reading into it what you wish it said instead of what it actually said.
[ link to this | view in chronology ]
Re: Re: Re: Re:
"The court found that Google could be liable for contributory infringement for failing to remove links when notified that they pointed to infringing material. "
but this:
"but intentionally linking to infringing content can create copyright liability"
is not an accurate restatement of that opinion and therein lies the problem. The court didn't find that linking is contributory infringement it found that failing to remove the links after being notified they were to infringing material could be contributory infringement. You're essentially trying to conflate the 'knowledge' being refereed to in the ruling, being actual legal knowledge as a result of direct notification, with 'common sense' or general knowledge, which is really nothing more than an educated guess or suspicion. Again, nowhere in that ruling, even the sections you've quoted, does it talk about links themselves constituting infringement it takes about lack of action after having knowledge opening the possibility of contributory infringement. It's like you're reading into it what you wish it said instead of what it actually said.
Last post, then I have to go. The court found that linking to infringing material could be contributory infringement once Google received notice that the link pointed to infringing material. As the court explained, once Google has that knowledge, it is imputed with the intent to cause whatever infringement occurs via the link. A person who intentionally links to infringing material doesn't have to be notified that their like points to infringing material. They already know this. So their intent to cause infringement via the link they provided can be imputed immediately.
I'm not conflating specific knowledge with general knowledge. Google becomes potentially liable when it knows a specific link points to infringing material. A person that knowingly provides a link to infringing material already has specific knowledge that the link points to infringing material. There's nothing general about it.
The ruling says that if Google continues to provide a link after it is informed that the link is infringing, then Google can be liable. Similarly, a person who provides a link to specific infringing material is already liable for that link because they already have the knowledge. Google needs to be told because otherwise they don't have the knowledge. A person that knowingly posts such a link doesn't need to be told anything since they already know.
You're the one not understanding the case.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
This is the point where your argument divorces it self entirely from what the case actually said into what you wish it said.
"I'm not conflating specific knowledge with general knowledge."
Yet you literally just did that in the sentences immediately proceeding this one. You want to pretend people 'already know' that it's infringing material without receiving notice but the court didn't rule that way. How would they get that knowledge without a notice? They simply cannot. Everyone needs to be told, not just Google, that's the whole point of the notice and takedown process. It's not 'well when you just know it's infringing and takedown.'
You're clearly not understanding the case, it talks about one situation: where google has specific knowledge as a result of a notice, and you want to pretend the ruling applies to another situation, where the linker has been given no knowledge and you just assume they have it because piracy.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re:
Google doesn't know the link points to infringing content until someone tells them.
But a person who on purpose posts a link that they already know points to infringing content ALREADY KNOWS that the link points to infringing content. No one has to tell them because they already know.
How can someone knowingly link to infringing material yet not know that they're linking to infringing material until someone tells them they are? That makes zero sense.
So when you say they cannot know, that makes no sense. I'm talking about people who do know and who post the link with that knowledge.
Sheesh.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re:
How do they 'ALREADY KNOW?' Legally that knowledge can only come from one place, the copyright holder, because only they know what uses are authorized. Did the copyright holder give them notice? No? Then HOW COULD THEY KNOW?
Of course it makes zero sense but it doesn't make sense because you're begging the question. You frame it as if they already know and pretend that's the end of it without asking how that premise came to be. I'm asking how that premise came to be.
It doesn't make any sense to you because you refuse to examine your assumption that they magically know already no matter how many times I point out that it's faulty.
Sheesh indeed.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re:
Are you serious? Under your logic, no one could ever be liable for willful infringement unless first told by the copyright holder that they were infringing. That's not how it works. A person can knowingly link to a work that they know to be infringing without the copyright owner being involved whatsoever. It's silly to say that a person can never know that a link they're posting points to an infringing work. People knowingly post such links all the time. If that's your best argument, I'm not persuaded.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re:
How can they know? You still haven't answered the question you just keep avoiding it and restating your premise. I've rejected your premise until you provide an explanation of how it comes to be and that explanation must include the copyright holder because they're the only ones that start with the knowledge. So how does it get from them to the person with the link?
This from the guy that assumes what he's trying to prove and then 'proves' it.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
I've having trouble telling if you're even serious with this argument. If I go to a file locker site, locate the link for a copyrighted movie that's in theaters or just come out on DVD, and then provide links to it so other people can download that movie, I know that I'm linking to an infringing video. You seem to think that copyright owner has to tell me it's infringing, but I'm saying that common sense is at play as well. If I know a movie is in theaters or just came out on DVD, I know that the file locker's copy is infringing. To pretend like I don't know because the copyright owner didn't explicitly tell me is ridiculous because it's not just what I actually know that matters--it's what I should have known that matters too.
I think you're missing that willful blindness is knowledge: "Willful blindness is knowledge, in copyright law (where indeed it may be enough that the defendant should have known of the direct infringement, Casella v. Morris, 820 F.2d 362, 365 (11th Cir.1987); 2 Goldstein, supra, § 6.1, p. 6:6), as it is in the law generally." In re Aimster Copyright Litig., 334 F.3d 643, 650 (7th Cir. 2003) (Posner, J.).
As the Supreme Court recently explained: Global-Tech Appliances, Inc. v. SEB S.A., 131 S. Ct. 2060, 2068-71 (2011).
So if I link to a movie in a file locker that I know to be in theaters or to have recently been released on DVD, I "subjectively believe that there is a high probability that" the work is infringing, and by not inquiring about the file's legitimacy I have taken "deliberate actions to avoid learning of that fact." So I'm willfully blind and the knowledge I avoided obtaining is imputed to me.
I agree that not every link to an infringing file would lead to liability. That was never my claim. But linking can lead to liability because the linker can be willfully blind to the fact that the linked-to file is infringing, even if the copyright owner hasn't told him that it is. If the copyright owner tells him, then it's just actual knowledge.
This comports with the DMCA safe harbors, which don't apply if the service provider has "have actual knowledge that the material or activity is infringing" or is "aware of facts or circumstances from which infringing activity is apparent." 17 U.S.C. 512(d)(1)(A)-(B).
The knowledge standard for contributory infringement is "know or have reason to know." In other words, actual or constructive knowledge suffices: A&M Records, Inc. v. Napster, Inc., 239 F.3d 1004, 1020 (9th Cir. 2001).
If I provide links to movies that I know are in theaters or recently released on DVD, then I have reason to know that those files I'm linking to aren't authorized. Therefore, I have sufficient knowledge to find me a contributory infringer.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
How exactly can you be a "contributory infringer" when the activity you are allegedly contributing to is not actually infringement?
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re:
I scan it, and put it up in cloud storage as per my right under first sale doctrine...
And then I put a link up somewhere so that others can see it...
Well, did I do anything wrong?
Remember, I bought the magazine, I can do what I want with it.
If I want to scan it and put it online, that's my business, I already paid money for it.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
But again, copyright is part of the larger plan, as we see every day.
[ link to this | view in chronology ]
That must come as heartbreaking news for Britt Dekker.
[ link to this | view in chronology ]
Appeal
[ link to this | view in chronology ]
Court rules against Supreme Court ruling
[ link to this | view in chronology ]
Re: Court rules against Supreme Court ruling
[ link to this | view in chronology ]
im a post this link on every dutch site i can
[ link to this | view in chronology ]
i am also curious as to whether the bias arse hole that ruled on other copyright cases in Holland was involved in this one?
[ link to this | view in chronology ]
Re:
Given this, the courts are perfectly able to come to different conclusions, particularly based on different facts.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
Pointing out something exists doesn't make you breaking the law.
Hey! Guess what! You can make Meth by buying up enough asprin!
[ link to this | view in chronology ]
Bit of a one sided piece
Thanks to geenstijl's idiotic actions we now have yet another bad judgement in a copyright case.
[ link to this | view in chronology ]
Re: Bit of a one sided piece
If they had been the ones to do this, do you think they'd be hit with an infringement lawsuit?
[ link to this | view in chronology ]
Re: Bit of a one sided piece
[ link to this | view in chronology ]
Re: Re: Bit of a one sided piece
[ link to this | view in chronology ]
Re: Re: Bit of a one sided piece
[ link to this | view in chronology ]
Maria...
[ link to this | view in chronology ]
I know I am late to this party, but I have to pick at this one a bit, because it's sort of a perfect piracy apologists view of the world.
When a ruling supports piracy in some format, it's a "sweeping judgement" or "changes everything". When it goes against piracy, it's narrow or (in this case) "highly fact specific". Sadly, none of it is true.
The reality is that a site that intentionally links to infringing content is infringing. These guys made it blatantly easy and obvious by linking and then relinking to the same file hidden on various file locker sites (gee, I thought file lockers were only for legal stuff...). They made it incredibly clear that their intention was to specifically link to infringing material with full knowledge.
What is interesting is that it sets up a whole potential for a precedent, at least in that country, that this is infringement. That could mean anything including embedded content.
I like how the court cut past all the horse crap that serial infringers through up there to block the law (I didn't host it, I didn't know, SODDI) and basically said that site owner did it, they know it, and they went back and re-linked again even after knowing the file was infringing. All the bull crap about where it was hosted at the moment is irrelevant to the intent of the site operator here.
Mike, you need to pay close attention here. As AJ has mentioned above, this is another decision in the world that is in line with other rulings and comments made in judgements. Infringement can and does happen in different ways, you cannot blindly ignore the ramifications of your actions, just because you are doing them "on the internet".
[ link to this | view in chronology ]
Re:
I'm late to your comment, but I have to pick at this one a bit, because anyone who uses the phrase "piracy apologists view of the world" is spouting bullshit.
When a ruling supports piracy in some format...
No ruling, ever, has "supported piracy in some format." Tautologically, a court ruling cannot "support piracy" in any way, shape, or form. The fact that you think it can, shows that you think perfectly legal things are "piracy."
..it's a "sweeping judgement" or "changes everything". When it goes against piracy, it's narrow or (in this case) "highly fact specific".
Funny, usually copyright maximalists accuse people of doing exactly the opposite. If it's not presented as "highly fact specific," but instead a "sweeping judgement" that "changes everything," the copyright maximalist camp accuses them of spreading FUD.
The reality is that a site that intentionally links to infringing content is infringing.
The reality is that a site that is told by the copyright holders of specific links on their system that point to infringing content, and do nothing to take those links down, then they can be liable for contributory infringement under civil liability theories.
Other than that, they're not infringing.
What is interesting is that it sets up a whole potential for a precedent, at least in that country, that this is infringement. That could mean anything including embedded content.
Aren't you doing exactly the same thing that you accuse the "piracy apologists" of doing? If a ruling supports copyright maximalism, it's a "sweeping judgement" or "changes everything." The plain fact is that the ruling is, in fact, fairly narrow.
I like how the court cut past all the horse crap that serial infringers through up there to block the law (I didn't host it, I didn't know, SODDI)
That's not "blocking the law." That's following it. If a site doesn't host the material, and/or didn't know it was infringing, then they are not infringing under U.S. law.
The fact that you view these sites as "serial infringers" shows, once again, that you think perfectly legal acts are "piracy."
you cannot blindly ignore the ramifications of your actions, just because you are doing them "on the internet".
This is complete bullshit, because these actions were not considered infringing until people were doing them "on the internet."
For example, the "linking sites" that we're talking about are no different than Hot Wacks. If you don't know, Hot Wacks was an annual magazine with discographies, mail-order contact info, and reviews, all devoted solely to bootleg recordings. It has been around since the 1970's, and the latest edition is still for sale on Amazon. And as far as I know, it has never been considered infringing. Yet somehow, when a website does the same thing, they're evil pirates who deserve to be arrested.
[ link to this | view in chronology ]
Can you please reconcile the following statements? I'm just trying to understand your thinking:
This is wrong. A contributory infringer is one who contributes to the infringement of another. They need not, themselves, actually infringe anyone's copyright to be considered liable. ... That case was significant because the MPAA had claimed that linking or embedding is direct infringement ... As it turns out, the MPAA was wrong. Big surprise there.
Patry is right in one sense - the "to authorize" phrase is designed to punish contributory infringers. It does this by making them no longer contributory infringers, but direct infringers.
It seems like you're saying that contributory infringers aren't direct infringers, but Patry is right because the Act makes contributory infringers into direct infringers. Huh?
[ link to this | view in chronology ]
Re:
Bad wording on my part. I should have phrased it: "It does this by making those who 'authorize' no longer contributory infringers, but direct infringers."
"Contributory infringement" is not the same as "authorization." Neither is "inducement" nor "vicarious infringement." All of these were taken from civil case law theories of secondary liability. None of the modern secondary infringement cases (Napster, Grokster, etc) were based on the idea that they "authorized" reproduction or distribution. They did not.
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
Any time.
[ link to this | view in chronology ]