The developers behind the Eden Switch emulator say they’re moving on from GitHub after the platform removed their repository in response to a copyright complaint from Nintendo. In new comments, the team described a post-takedown plan built on self-hosting and mirrored code, while criticizing what they characterize as a lack of due process for their counterclaims.
Eden Says GitHub Ignored Counterclaims After Takedown
According to the Eden team, they anticipated Nintendo’s latest wave of DMCA takedowns targeting Switch emulators on GitHub and had already duplicated their code and assets off-platform. They also say they filed the legal paperwork designed to resist a takedown, including counter-notices meant to trigger restoration of the repository under the DMCA’s 10–14 business day window if no lawsuit followed. The developers contend GitHub did not acknowledge those filings and removed the project as soon as Nintendo complained.
GitHub, owned by Microsoft, outlines a counter-notice process in its public DMCA policy, which mirrors U.S. law: when a valid counter-notice is received, content may be restored unless the rightsholder initiates legal action. However, platforms can make judgment calls, especially in disputes that may implicate anti-circumvention provisions under 17 U.S.C. §1201. Eden’s comments underscore a growing frustration among emulator teams that feel the balance has tipped toward immediate removal.
Nintendo’s Crackdown And The Stakes For Emulators
Nintendo has a long record of protecting its intellectual property and anti-piracy measures, particularly around active platforms. The Switch remains a top seller, with lifetime sales surpassing 139 million units by company reports, giving the firm strong incentives to challenge tools it associates with piracy. Earlier this year, the high-profile Yuzu case ended with the emulator’s shutdown and a $2.4 million settlement, a result that sent a chilling signal through the emulation scene.
Legally, emulation sits in a nuanced space. U.S. case law has held that emulators themselves can be lawful when independently developed and shipped without proprietary code. But distributing encryption keys, firmware, or tools that bypass technological protection measures often triggers DMCA anti-circumvention concerns. That gray area is where many Switch projects get ensnared, even when they avoid bundling Nintendo content.
Cloned Repos Keep Development Moving Off GitHub
Eden’s developers say the project will continue via a cloned repository hosted outside GitHub. While some links still point back to the shuttered GitHub pages, the team notes that the source code is available for anyone to compile, and those willing to dig can find prebuilt Android APKs. They also maintain an archive of older builds to preserve work predating the takedown.
The team does not expect to return to GitHub. Instead, it’s leaning into a decentralized strategy—self-hosting the main repo and relying on community mirrors to reduce single points of failure. It’s a model other emulator projects have adopted after prior takedowns, with devs increasingly turning to independent Git platforms or read-only mirrors to safeguard continuity.
Costs And Community Support For Self-Hosting
Self-hosting isn’t free. Eden warns that bandwidth spikes and storage for build artifacts can add up, particularly when a project’s visibility increases after a takedown. The team is directing supporters to donation channels to offset infrastructure needs and maintain steady development velocity.
For users, this likely means fewer one-click downloads and more DIY compilation, at least in the near term. For developers, it means additional time spent on ops—standing up mirrors, maintaining CI pipelines off GitHub, and fielding legal questions—time that would otherwise be devoted to performance work, rendering fixes, and game compatibility.
What It Means For Android Emulation Going Forward
On Android, Switch emulation has matured rapidly, with handheld-centric optimizations and controller mapping becoming table stakes. Projects like Eden and others have pushed mobile GPUs hard enough to get a surprising number of titles booting, if not always at full speed. But legal headwinds are reshaping the ecosystem: repositories vanish overnight, precompiled binaries become harder to find, and users are nudged toward compiling from source and managing their own firmware dumps—steps that reduce casual misuse but also raise the bar for legitimate tinkerers.
Advocacy groups such as the Electronic Frontier Foundation have long argued for clearer exemptions around preservation and interoperability, while platform holders emphasize protecting active revenue streams and anti-piracy technologies. Until that policy gap closes, projects like Eden will live with the constant risk of platform lockouts and will architect around them.
The Road Ahead For Eden After GitHub Takedown
Eden’s message after the takedown is pragmatic: development continues, but distribution is changing. The code is out there, the team is reorganizing its pipeline, and community mirrors are rising to fill in gaps. Whether that’s enough to keep momentum will hinge on sustained contributions, careful legal hygiene, and the willingness of Android enthusiasts to compile and test outside the convenience of GitHub’s familiar workflow.
