Nintendo only cites section 1201 in their DMCA takedown request: https://github.com/github/dmca/blob/master/2026/11/2026-11-0...
Same thing seems to have happened with Take Two submitting takedown requests yesterday[0] for software projects that enabled you to run GTA 5 on Apple hardware if you bring your own copy, although this is a much less legal-looking takedown.
0: https://github.com/github/dmca/blob/master/2026/11/2026-11-1...
> We adamantly request that GitHub disable the repositories and all associated forks from the platform. We emphasize that “bring your own files” disclaimer does not automatically shield the user from secondary copyright infringement through clear intent to facilitate the act.
> Section 512(c) provides protection only from liability for copyright infringement. Plaintiffs seek to hold defendants liable not for copyright infringement, but for a violation of Section 1201(a)(2), which applies only to circumvention products and technologies. Section 512(c) thus does not apply here.
So in essence taking down a repository would not absolve GH of liability for the 'trafficking' of said circumvention technology.
Although it looks like GitHub has their own policy for handling circumvention claims: https://docs.github.com/en/site-policy/content-removal-polic...
I do wonder if this extra circumvention review was undertaken by GitHub though, given I haven't seem any evidence of the extra process happening (giving the repository owner a chance to respond or modify their repo / referring the developer to legal consultation via GitHub’s Developer Defense Fund).
They took down a fork which had a lot more than the firmware itself.
1. A uniform baseline that developers could develop against. This is a real problem with PC gaming; and
2. The proprietary hardware provided a decent amount of protection against piracy. It's never been impossible but it tended to be less accessible such that a whole bunch of people just didn't bother.
Because of the lock-in this allowed hardware manufacturers to sell consoles as near or even below cost because they'd make the money back on games.
I think AI has killed (2). Like there were PC ports of the remastered Ocarina of Time the same week it was released. There's no putting that genie back in the bottle.
So the PS5 is fairly long in the tooth. It's 6 years old. The PS4 lasted 7 years but there's just no talk of a PS6. That's probably delayed somewhat by the RAMpocalypse but if it were coming I think we'd know something by now. I really wonder if there's ever going to be a successor to the PS5 or Xbox (or Switch 2).
I really don't know where gaming as an industry goes from here.
In this case, do the security checks to allow authorized software to run on a console constitute TPMs protected under the DMCA?
Picofly is a clean room firmware written for an entirely separate chipset to Nintendo's Switch/2. It contains no copyrighted assets. Its explicit purpose is to allow the system to load unsigned payloads.
Is the precedent going forward that any general-purpose unlock tool that grants owners root access to hardware they legally purchased will automatically constitute unlawful trafficking in technology designed to bypass digital locks under 17 U.S.C. § 1201?
On the other hand, an Australian court ruled the other way, as did the Italians.
[1]: http://news.bbc.co.uk/1/hi/technology/3915179.stm
[2]: http://news.bbc.co.uk/1/hi/technology/4315172.stm
It's an ongoing part of "right to repair". Hardware manufacturers are increasingly looking into ways to extract more money and with the slowdown in performance and increase in hardware costs that means they are looking elsewhere.
These companies are almost certainly thinking of and looking towards planned obsolescence as the mechanism to force their customers to repurchase new hardware barely different from the old hardware. Sony shutting down the PS3 store is going to be the move for others.
End users hacking their hardware and making the software they purchased still usable after the obsolescence period cuts right into those plans.
You’ve got to understand, the people flipping the switch on and off aren’t students of the law[1].
My guess is the buck was passed to a bunch of incompetent folks. They saw the repo has a low number of stars and doesn’t belong to a company, figured there was a low risk of blowback, and concluded there was no need to escalate to actual competent folks (aka in-house counsel).
They may have had a playbook, but when it comes to moderation, a lot is left to how the individual interprets the rules. The real scrutiny on their end would happen now if enough of us complain about this.
[1] AI music company claims copyright over musician's own recording, gets her YouTube video removed - https://www.reddit.com/r/technology/comments/1xyi3bu/ai_musi...
Does anyone actually think that a mod chip for a DVD player allowing disc dumping would be exempt under the DMCA? DVD circumvention was basically the entire reason we have Section 1201 to begin with! There's also the aspect the statute does not differentiate, in any way, between software methods versus hardware methods for circumventing access controls.
(You may have never read the fine print, but VLC has always had a warning to US users saying their DVD decryption is probably a violation.)
Its also why for anything that interacts with a system that MIGHT be called a bypass, to host it on Gitflic.ru and tell them all to fuck right off.
140+ Repos are pulled under Safe Harbour justification based on an unchallenged accusation. Github only reinstated youtube-dl after the EFF did some basic due diligence. The Github Developer Defense Fund to help open-source developers respond to unwarranted DMCA Section 1201 claims is a paltry $1 million.
Ryan Daly tried to defend himself in the MIG-Switch case and ended up settling for $2 million. The Yuzu devs ended up settling for $2.4 million.
The 9th Circuit (which github falls under) reversed previous decisions and said any circumvention - even for lawful purposes - is illegal regardless of copyright infringement. This would suggest that the presence of ANY copyrighted code on ANY physical product automatically grants the weaponisation of copyright law to deny aftermarket repair or any other use-cases of actual ownership.
The scarier question then becomes - when will Intel or Broadcom or Nvidia start suing people for unlocking their hardware?
Hosting the repo either in China or Russia, outside of the US's sphere of DMCA-like laws is the proper play here. Of course, use some random name as well that's only used on those repos.
The law is absolutely wrong, and should NOT be respected.
You can safely assume you're preaching to the choir on these matters with Hacker News.
Your position, however, doesn't represent an inviolable workaround.
Even if a foreign host ignores a DMCA notice, a copyright owner can still pursue infringement claims directly against a US developer in the US, or pursue it on similar local copyright laws in the host's country.
As explicitly related to this case, 17 U.S.C. § 1201 legislates that it is illegal to manufacture, offer to the public, provide, or otherwise traffic in circumvention tools. Writing the code, maintaining the repository, or uploading it from a computer inside the United States constitutes domestic conduct, giving U.S. courts jurisdiction regardless of where the remote server sits.