Details Of The Rapidshare Decision: No Search Engine, Plus Efforts To Takedown Copyright Material Helped
from the but-it's-not-a-complete-win dept
Earlier, we wrote about the ruling against Perfect 10 in its attempt to get a temporary restraining order on Rapidshare. As we mentioned at the time, the only details we had were based on Rapidshare's press release, that obviously presented it in the best possible light to Rapidshare. Thankfully, Christopher Harbin alerted us in the comments that he's posted a copy of the ruling and written up his own analysis. First, here's the ruling:That said, there are some interesting things (not all good) in the ruling. There were a few things that helped Rapidshare here. First, is that it does do things to takedown content it believes to be infringing. Second (and perhaps most interesting) is the fact that it does not index or promote the content stored on its service by itself. Since most file sharing services include a search engine aspect, the court concludes that this is a key element of suggesting that Rapidshare is not liable for direct infringement. That's an interesting ruling that could answer the question I've asked before about whether or not it actually is possible to create a site that allows for sharing of files that does not run afoul of the Grokster inducement rules.
The other thing that helps Rapidshare is that, despite being involved in a whole bunch of copyright cases, it still appears that Perfect 10 is somewhat incompetent in understanding copyright law and availing itself of tools to deal with infringement. In this case, Perfect 10 didn't send Rapidshare the specific links where infringing content existed. It just sent the company a bunch of files, but Rapidshare had no way to match those files to ones hosted in users' lockers. Even then Rapidshare still did try to find as many of the images as possible, even going so far as to do Google searches, and delete them. On top of that, Rapidshare has a tool that lets content owners indicate if certain files are infringing. Perfect 10 chose not to use that.
The one part of the ruling that I found troubling, however, is that the court did say that, even without being alerted to what's infringing, Rapidshare did have "specific knowledge" of infringing works on the site. This is a key point of dispute in the Viacom/YouTube case, where Google makes the argument that there's no way for it to know which works are really infringing and which are there on purpose. Yet, in this case, the court says that the service provider does have specific knowledge:
Thus, it appears that specific knowledge of direct infringement may exist even where an operator does not have information that would allow it to search its contents and distinguish infringing from non-infringing materials. Here, RapidShare received notice of hundreds of copyrighted Perfect 10 images that were found on its servers. The Court therefore concludes that RapidShare had actual, specific knowledge of direct infringement.Basically, it says that because Perfect 10 alerted Rapidshare to infringing content, then Rapidshare has "specific knowledge." That wasn't enough to meet the full inducement standard, so isn't a huge issue here, but that logic seems wrong to me. If that's all it takes to create "specific knowledge," then lots of user-generated content sites could be in trouble. So, if you want to cause trouble for any UGC site, you just upload content, and then alert the site that there is infringing content on the site, but don't tell them where it is or how to find it. I don't see how that's "specific knowledge" at all, but the court felt otherwise.
Finally, while I appreciate Christopher's analysis of the ruling, I have to disagree with his first two points. He doesn't understand why not having a search engine matters:
Although Rapidshare does not index its files, it basically punts indexing to third-party websites. It’s trivial to find infringing material hosted on Rapidshare and other file-hosting sites and I’m not sure why dicing up storage and indexing into separate entities which obviously have a symbiotic relationship should be able to avoid liability.I think that's a slight misread of the ruling. It's not saying that Rapidshare gets to avoid all liability. It's just that it takes away Rapidshare's direct infringement liability, because it is not, in fact, setup to make it easy for people to find that content. The fact that others have made it easier to find that content should not be blamed on Rapidshare.
Second, Christopher notes:
I'm not at all convinced that in all cases plaintiffs should be forced to ferret out all infringement on a defendant's website. As the law stands right now, copyright holders have to employ an army of people to constantly monitor defendant's site for infringement.To which the obvious response is, why should that burden fall on the defendants? If it takes plaintiffs "an army of people," it would actually take the defendants significantly more than that, complicated by the fact that the defendant has no way of knowing if the content has been uploaded legitimately or is an infringing copy.
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: copryight, dmca, infringement, liability
Companies: perfect 10, rapidshare
Reader Comments
Subscribe: RSS
View by: Time | Thread
Why the screwy display of the ruling?
[ link to this | view in thread ]
Re: Why the screwy display of the ruling?
Um. Blue link that says "posted a copy of the ruling" is, in fact, the PDF. Also, the DocStoc setup has a link that clearly says "download." So it's there twice.
[ link to this | view in thread ]
Re: Why the screwy display of the ruling?
Tho, after Mike's response, I'm guessing you wish you didn't even say anything at all?
[ link to this | view in thread ]
It also seems like an easy way to force companies to waste money and resources money by making them look for items among their own content that may not even exist. I could see media companies uploading as much data as possible through shills, subtly obfuscating it in a number of ways, then sending mass notices without any location info simply to tie up the hosting company in court, force them to waste money, and exert pressure to capitulate to legal agreements.
What? Viacom's already doing this? My bad...
Official Notice: Some of your bits are infringing. Which bits? That's for you to find out! Change them or we'll see you in court.
Have a nice day
[ link to this | view in thread ]
Re: Re: Why the screwy display of the ruling?
[ link to this | view in thread ]
waitwaitwait
[ link to this | view in thread ]
Re: waitwaitwait
[ link to this | view in thread ]
Reporters are not experts, very true.
Perfect, and many examples of this effect can be found on this web site !
The difference is most take the time to get familiar with the subject matter, or do the necessary research prior to writing.
But Mike, for you it's an impressive introspection :)
And some, well,,,, dont..
[ link to this | view in thread ]
Re: Reporters are not experts, very true.
Of course, many people prefer to be generic, and wildly throw accusations around without any specific details.
[ link to this | view in thread ]
Re: Reporters are not experts, very true.
[ link to this | view in thread ]
Re: Re: Why the screwy display of the ruling?
not that i mind, i tend to skip over the documents myself...
[ link to this | view in thread ]
To be fair the court did not actually rule one way or the other on the DMCA issue, they simply said they felt rapidshare was "unlikely to succeed" in using the safe harbor affirmative defense, but still very worrisome.
As to the issue of "specific knowledge" this too seems like a stretch. Being notified that there "is infringing content on your network" seems much more akin to GENERAL KNOWLEDGE to me, specific knowledge would be more along the lines of LOCATION of the infringing content on your network. In this matter the court seems to contradict itself since they find that rapidshare is not guilty of distribution or direct infringement because they do not know or make available the locations of specific files yet despite this fact finds them to have specific knowledge of infringing activity.
Thankfully the court did NOT find that they were guilty of contributory infringement (of which the specific knowledge of infringement was a pertinent fact) because rapidshare had taken "simple measures" to prevent infringement:
Considering the evidence submitted by the parties thus far, the Court concludes that Plaintiff has not shown that RapidShare is failing to take simple measures to prevent further damage to Plaintiff’s copyrighted works. Rather, the evidence suggests that RapidShare is using information provided by Plaintiff to locate and remove infringing materials, and is also taking independent steps to identify, locate, and remove infringing files. Accordingly, the Court concludes that Plaintiff has not shown that RapidShare is contributorily liable for copyright infringement under the standard announced in Amazon.com,
So if rapidshare had known there were infringing files on their service, even if they did not know the specific locations of those files, and had failed to take any measures they likely WOULD have been found to be guilty of contributory infringement.
[ link to this | view in thread ]
crimping tools
Manufacture crimping tools, wire stripper, cable cutter and hydraulic tools.
http://www.fivestar-tools.com
Manufacture hydraulic crimping tools, gear puller, cylinders, pipe bender, hole digger, busbar processing machine, hydraulic pumps,wire stripping machine and hydraulic hose crimping machines.
[ link to this | view in thread ]
One can easily search the net and find RapidShare generated URL's associated with files that only one intellectually challenged to the point of having the IQ of a rock would fail to realize is illegal content. Seriously, a URL having in its title "Adobe Photoshop CS5 plus keygen, crack, and working serial number" is much more likely than not to actually have such a file being hosted. Could it be a phony title? Perhaps. Is it likely a phony title? Probably not. A simple download of such files tends to demonstrate time and time again that such titles are almost universaly reflective of the associated work.
RapidShare does appear to follow practices responsive to notices that identify such files with sufficient specificity that they can be found and examined, but this alone does not necessarily address RapidShares "Achilles' Heel".
Yes, RapidShare does follow an approach that serves to reduce its exposure to legal claims associated with copyright infringement, but its approach if far from bullet proof.
If copyright holders do in fact have the ability to scour the internet for infringing material hosted on RapidShare, as well as a the presence of a take down tool, it is hardly a stretch that the site employ an automated system performing both these functions without human intervention.
What I find particularly sad it that sites like RapidShare and a few of the myriad of torrent search engines constantly find themselves in the "copyright bulls-eye" precisely because so many persons using them seem unable or unwilling to conform their conduct to the requirements of law.
[ link to this | view in thread ]
who is running a business based on infringement? it isnt the copyright holder. it is the file share site, which profits from the sharing of content. who else should be responsible? if they want to be in the file sharing business, the risk of illegal content being shared is part of the business, and the costs related to stopping it part of that business.
[ link to this | view in thread ]
Hilarious!
BECAUSE THEY ARE THE ONES MAKING MONEY FROM IT!
Rapidshare wants all of the benefits and none of the responsibility.
And as usual, you take on the role of their tin pot mouthpiece.
[ link to this | view in thread ]
Re:
On top of that, having such a process in place would make the company a prime target for lawsuits regarding anything not found and removed, and they would probably have a less compelling defence than they have now.
[ link to this | view in thread ]
Re:
They may not have DMCA agent registered, I don't doubt they will soon, but they do respond quickly to being notified of infringing content.
Here's the point you miss: They don't know what is infringing and what is not. They don't know who works for company X and is authorized to post their content or who doesn't. It is not possible for them to police infringement based on that alone which is why the legal burden, outside of inducing infringement, is not on the service provider but rather the rights holder. The service provider simply has no way of knowing. And since Rapidshare isn't inducing infringement they win. The risk of illegal content is a factor in the file hosting business but since they host cannot know what is infringing and what is not then they cannot be required to police it. As long as they remove content when notified, a morally questionable practice in my opinion since it steps around due process, they are not liable.
Guess you missed how the law actually works.
[ link to this | view in thread ]
LOL!
[ link to this | view in thread ]
Is RapidShare Really Different? US and German Courts Seem to Think So
[ link to this | view in thread ]