4 ms·
Part of the challenge here is that "the DMCA" is a number of clauses. People who are "against the DMCA" often turn out to have an incoherent position, at least
by jerf 9y ago
Part of the challenge here is that "the DMCA" is a number of clauses. People who are "against the DMCA" often turn out to have an incoherent position, at least from a legal standpoint, when it turns out they just disagree with one of the contentious clauses.
This would in fact be the most contentious clause, the one about being able to take down tools that enable circumvention, the one that is historically the one that perturbs techies and HN-types the most. I think what we see here isn't so much a DMCA takedown of a single line, but a single line modification in an attempt to prevent someone trying to take down the entire ad blocker, by making it so this particular person doesn't have any standing (in the legal sense) to make claims against the ad blockers anymore.
The copyright takedown clause would be number two, but it has a mitigating factor; the DMCA copyright takedown process that you might see on a hosting site or HN itself [1] has a positive element as well, which is that by conforming to the DMCA a site like HN is able to host user content like our comments while discharging from themselves the responsibility of having to pre-filter every comment for copyrighted content. This clause has certainly been abused, and there is a justifiable case that the Feds have not been adequately aggressive about chasing them down, but on the net I still approve of this clause, personally.
(You also have to distinguish between "the DMCA" and a site's policy, which may go above and beyond. Many or most of the things that people complain about for YouTube, for instance, are their own elaborations on the theme, not the legal requirements themselves. Not all of them, though; YouTube tends to favor the big media companies very strongly when it comes to defining "fair use". But things like taking away your monetization and giving it to somebody else is a YouTube policy, not the DMCA. Or at the very least, it's a penumbric emanation of the DMCA and not the DMCA itself.)
Were I the developers or anyone with any ownership in this software, I would hesitate on putting too much stock in the idea that this was an improper use of the DMCA claim process. It was. But the reward for aggressively pushing back on that may be a proper lawsuit for violation of the anti-circumvention clauses, for which there is not a notification process but simply a legal basis for lawsuits granted, IIRC. Your reward for armchair-lawyering this DMCA takedown request could be a true lawsuit.
[1]: https://news.ycombinator.com/dmca.html https://news.ycombinator.com/dmca.html - have a look at the footer of this page
- jrochkind1 9y agoThe DMCA does make distributing circumention measures illegal, but I can't find anything in the law, or discussions of it, saying that the takedown process applies to circumvention measures. The takedown process says an ISP like Github is not liable for copyright infringement if they respond to takedown notices, which is what creates the takedown process. It doesn't say anything about circumvention measures and liability with regard to notices though. What the DMCA says about circumvention measures: > (2) No person shall manufacture, import, offer to the public, provide, or otherwise traffic in any technology, product, service, device, component, or part thereof, that— > (A) is primarily designed or produced for the purpose of circumventing a technological measure that effectively controls access to a work protected under this title; > (B) has only limited commercially significant purpose or use other than to circumvent a technological measure that effectively controls access to a work protected under this title; or > (C) is marketed by that person or another acting in concert with that person with that person’s knowledge for use in circumventing a technological measure that effectively controls access to a work protected under this title. It seems obvious to me that Easylist is not such, I don't think it meets A, B, or C. But it'd be an expensive court process and who knows what the court would end up doing. In this example, it seems like Easylist has no desire to include that URL anyway, as it is not an ad server. It may be true that Github can decide to refuse to host the thing anyway, but it's not a DCMA takedown notice process. The whole situation is indeed a mess.
- jerf 9y agoAs I added after you replied, I agree that this is an improper use of the takedown procedures. However, your reward for successfully armchair-lawyering that may be a full-on Federal lawsuit. Also, I agree that Easylist itself may still not be a lawsuit target. It simply makes a claim about a certain domain, it doesn't do any access circumvention itself based on that claim. But if Easylist isn't, the ad blockers using it certainly would be. And that alone would change the dynamics of the situation quite a bit. I hate to say it because I like adblockers too, but it is frankly very likely that when the advertising industry finally makes the push against them that by current law, it will indeed turn out that it is illegal to use ad blockers on sites that take active measures to ensure you view ads [1]. Again, don't mistake me saying this for endorsing it, but I think it's a very plain and obvious reading of not just the DMCA, but even something as fundamental to our legal system as common-law contracts... if a website wishes to make viewing their content conditional on viewing an ad, they can do that, just as they can make viewing their content conditional on paying them money, joining a club, or anything else that qualifies as "consideration" [2]. They can also place further restrictions on that content as part of that content. Any argument in favor of ad blocking that would also explain why either Netflix customers have the legal right to retain copies of the movies, or in the most extreme cases, explain why everybody has the legal right to retain copies of Netflix movies, should be discarded as an argument that proves too much [3]. I'd suggest the ad blocking community and the interested tech community at least wargame out the plan for if they lose the legal cases, because I would personally put that at somewhere around 90% probability if any of them ever go to court. Even with the EFF supporting it, I fear the EFF would pretty much be reduced to making very handwavy arguments about fundamental rights and basically pounding on the table, because in my considered opinion they really won't have much else. And even if they are correct, courts tend not to take much account of those arguments. [1]: If the judgment goes really bad, it could even be illegal to bypass sites that don't try anything explicit. However there is a very good argument here that there is a history on the internet of assuming more rights rather than fewer if you don't assert yourself, such as the fact that browsers generally render things differently anyhow, the long history of search engines, the needs for accessibility software to render pages fundamentally differently anyhow, etc. I think there's a good chance no judge would want to overturn that consensus as it's now around 25 years old. [2]: https://en.wikipedia.org/wiki/Consideration https://en.wikipedia.org/wiki/Consideration [3]: http://slatestarcodex.com/2013/04/13/proving-too-much/ http://slatestarcodex.com/2013/04/13/proving-too-much/