Live data from Hacker News

A Better DMCA Process

github.com

31–35 of 35 posts

Re: A Better DMCA Process

#31
post #3

This is interesting because the DMCA process is, as I understood it (as a paralegal working on DMCA issues in a past life), a fairly rigid prescription that provides a safe harbor for providers like GitHub, ISPs, YouTube, etc. The simplified version of the process: 1. The party claiming to own the rights to copied content submits a well-formed DMCA takedown notice to the listed DMCA agent contact information of the p…

If that's the law, then why isn't content from various large companies vanishing (and later reappearing, as in part 4) from the web all the time?

Pick any large company. Surely somewhere among the 7 billion people in this world is someone who (1) hates that company, (2) can put together a well formed DMCA takedown notice, and (3) is willing to give it a shot.

Following that, if your description of the law is correct, the specified content must be taken down, at least temporarily.

So why don't we see major corporate web pages & content disappearing & reappearing on a daily basis?

Re: A Better DMCA Process

#32
post #3

This is interesting because the DMCA process is, as I understood it (as a paralegal working on DMCA issues in a past life), a fairly rigid prescription that provides a safe harbor for providers like GitHub, ISPs, YouTube, etc. The simplified version of the process: 1. The party claiming to own the rights to copied content submits a well-formed DMCA takedown notice to the listed DMCA agent contact information of the p…

If someone took my sourcecode and posted it up on github without my permission, I'm not entirely sure I'd agree that that stance is 'customer friendly'. Only the infringing customer wins in that scenario.

Re: A Better DMCA Process

#33

Earlier quoted context omitted.

Is there a mechanism they could use for blocking access to the file from within git without rewriting all of the commits (and therefore changing hashes)?

I'm not sure I completely understand your question, but my guess is they are blocking access to the file from github.com which is all they need to do to comply with the DMCA request. They can't do anything about people's local copies.

Sure, they can block access to the file from their web interface. I'm asking how they block access to a specific file when someone does a "git clone" or "git pull".

Re: A Better DMCA Process

#34

I can't help but think of the Snapchat breach. Surely the world understands that once something is on the internet, it's there forever, right? Complying with the DMCA is security theater at best, and at worst, stifling to innovation. I mean, we have many laws centered around the difference between intentionally and unintentionally inflicting harm on others. So for example if you break someone’s rib performing CPR, yo…

> If GitHub complies with the DMCA and we use GitHub, then we are quietly endorsing the DMCA. I happily endorse § 512 of the DMCA. Not only is the safe harbor provision a well-balanced law for all parties involved, but it's the only thing that makes startups that host UCG legally viable. Without the DMCA, Github could not exist. They'd be personally liable for every copy of every file they distribute without a copyri…

I was surprised to get down voted for my comment, but, that's a perfect example of the chilling effect that the DMCA has had upon discussing freedom in the information age.

What the DMCA (and similar IP law) gets wrong is persecuting sharers with "intent to distribute". Copyright law was originally intended to protect creators from other people profiting off of their work by copying it. I'm all for the government cracking down on bootleggers.

But I’m very much against the notion that we should go after people who use or view content that is already publicly available. To use your example, the MPAA could and should go after someone who leaks a movie online. But, they should have to prove that the person profited in some way from his or her actions (and correspondingly, the penalty for doing so should be somehow proportionate to that profit). Individual users who share the movie on BitTorrent are not breaking copyright law, because they are not selling copies. It’s really that simple. I personally don’t think that it’s the government’s responsibility to devote resources to tracking down sharers, and certainly not to prosecute them. If we want to consider laws regarding “stealing” intellectual property, we can certainly do that as a society, but that has nothing to do with copyright (trademarks or patents either).

And to be clear, the only thing that new IP laws could address is the potential lost income of content producers. But, there is no way to prove that a sharer would have paid to view that work in the first place. I personally think that this flies in the face of free market economics. The government’s role is to create and manage a fair playing field for all players. So if it is going to start prosecuting thought crime, then it needs to remember its duty and crack down on monopolies and the bribery (ahem, lobbying) that props up media corporations with lifetime-length copyrights and the loss of the public domain through the use of paywalls (among other things). So the DMCA put the cart before the horse by not reinstating the Sherman Antitrust Act, not setting realistic limits on copyright and other IP laws, etc. The DMCA has done nothing to increase the income of new artists, and everything to further enrich established media corporations like Disney (I would argue by design).

We need to also consider that courtrooms and juries are the most important link in the legal chain. By not hearing every case in a court of law, we are passing the burden to individuals to prove their innocence against large institutions (by settling out of court, since they simply can’t afford to lose). I think this flies in the face of the notion of innocent until proven guilty. Whenever I see another child or elderly person being prosecuted for file sharing, it strikes me as being closer to extortion than justice.

So to summarize, I don’t recognize “§ 512 of the DMCA” as necessary or even valid, because ISPs and hosting providers that don’t sell the copies they store are not breaking copyright law in the first place. A website that charges money to view HBO Go’s stream is breaking the law. A website that provides a storage space for a file is not. So the DMCA was not necessary in the first place, and we should be enforcing the laws that are already on the books before creating new ones.

My hope for the future is that we reduce copyright and patent periods to something reasonable like 5 or 10 years, only cover works by copyright (so physical records, books, paintings, movie reels, etc, not bits), invalidate all process patents (so no software, business or medical patents), make it illegal to create laws regarding DRM schemes (in other words, leave it up to the private sector to fight the arms race against cracking), and force worries about whether a work is fair use to be heard in court (judged by people, not metrics). Then I hope that we bring back the Fairness Doctrine to promote broadcasts that are in the public good (real news, not infotainment), more funding for public television and teaching art in school, and bar prosecution for using works for educational and nonprofit purposes.

I think this is a case of, what you are saying about protections for businesses (both producers and carriers) has some validity, but for me, democracy, personal freedom and liberty come first. I don’t want to live in a country where we can be shaken down by corporations because they are worried about their bottom lines.

Re: A Better DMCA Process

#35

Earlier quoted context omitted.

I'm not sure I completely understand your question, but my guess is they are blocking access to the file from github.com which is all they need to do to comply with the DMCA request. They can't do anything about people's local copies.

Sure, they can block access to the file from their web interface. I'm asking how they block access to a specific file when someone does a "git clone" or "git pull".

It sounds like they just wait 24 hours to get contact.

"because GitHub cannot disable access to specific files within a repository, we will contact the user who created the repository and give them approximately 24 hours to delete or modify the content specified in the notice. We'll notify the copyright owner if and when we give the user a chance to make changes."

re: https://help.github.com/articles/dmca-takedown-policy/

Post reply on HN