Am I Violating The DMCA By Visiting The NYTimes With NoScript Enabled?

from the simple-questions dept

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

As we continue to explore the NY Times' bizarrely pointless paywall , it comes as no surprise that the wall itself is barely any wall at all. It's not even a fence. It's basically a bunch of fence, and someone screaming: "Pay no attention to your own eyes. There is a fence here, and you should go round the front and pay at the entrance... unless someone sent you here. Then walk on through." That, of course, is bizarre, and it means that most people will never actually see any fence at all. But it gets even more bizarre when you discover that the "paywall" itself has apparently been written in javascript , meaning that when you do hit the wall, the full article you want to read actually loads in the HTML, it's just then blocked by some script asking you to pay up. That means it's even easier to remove than many had predicted (no need to even delete cookies or any such nonsense). In fact, that link above points people to NYTClean , a four-line javascript bookmarklet, that makes it easy to remove the paywall with (literally) the click of a button, should you actually encounter it.Now, when I read that, my first thought was that certainly sounds like a "circumvention device" under the DMCA. The author is Canadian, so he may be protected for now, since Canada (thankfully) doesn't yet have an anti-circumvention clause that makes any such circumvention tool illegal -- though, the Canadian government is still apparently considering a law that would add just such a clause. Of course, to anyone who understands what's going on, that's ridiculous. Four simple lines of code to remove a javascript popup should not be considered a tool for infringement, but it is.Of course, that got me wondering. I tend to use the always excellent NoScript extension when browsing, which turns off javascript, except on a few key sites where I enable it. If the stories about the NYT paywall being done in javascript are true, then I'll simply never run into it, no matter what I do.So, here's the question: have I broken the law by using NoScript? I've used it for years, and it seems pretty ridiculous to claim that I now need to specifically go and whitelist the NYTimes just because it wants to hit me with an incredibly porous paywall. But, technically, I could see how an argument could be made that merely using NoScript makes me a DMCA violator by "circumventing" technical protection measures. Does this also mean that NoScript -- an incredibly useful tool -- has suddenly become a "circumvention device" overnight, because the NYTimes programmed an incredibly stupid paywall in javascript?What this really should highlight is the massive problem with automatically outlawing all "circumvention" and "circumvention devices." It leads to particularly dumb situations like this, when a clueless newspaper puts up an amazingly poorly thought out paywall in a manner that makes very little sense.

Filed Under: dmca, javascript, noscript, paywall

Companies: nytimes