For quite some time now, we’ve been concerned about the continued expansion of “secondary liability” concepts, adding more and more liability for copyright infringement to parties who are often far removed from any actual infringement. There are two major concerns with this. First, putting liability on one party for the actions of another just seems generally problematic. But, perhaps more importantly, when you put potential liability on an unrelated party, the end result is almost always excessive policing in a manner that hinders or entirely blocks perfectly legitimate activity and speech.
That’s why a recent court ruling in Germany is so problematic. It’s the followup to an earlier ruling that found a domain registrar, Key-Systems, liable for actions done by the users of a torrent tracking site H33T. H33T just hosted the torrent (which, we should remind you, is not the actual infringing file), and some users used that tracker to torrent the album Blurred Lines. When H33T failed to respond to a takedown notice, Universal Music went after the registrar, and the court said it was Key-System’s responsibility to stop the infringement. Of course, the only way for the registrar to do that is to yank the entire domain.
The case was appealed, but the appeals court upheld the lower court ruling. Even though the registrar pointed out (accurately) that it had no way of knowing if the torrent was actually infringing, the court said that the registrar was responsible for assuming it must be infringing once it had contacted the domain owners and not received a response. That’s an interesting shifting of the burden of proof. The court also seems unconcerned that the only way the registrar can remedy the situation is to take everything down, saying that if the website didn’t want this to happen it should have responded promptly to the takedown notices it had received.
Read the Full Article: Source – Tech Dirt
https://www.techdirt.com/articles/20141108/07010229086/sending-liability-up-stack-domain-registrars-potentially-liable-infringement-end-users.shtml
Leave a Reply
You must be logged in to post a comment.