Nintendo takes Picofly firmware down from GitHub [video]
https://www.youtube.com/watch?v=-TLCGUpoD6cIn 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.
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.
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.