this post was submitted on 05 Mar 2024
154 points (77.5% liked)
Open Source
31197 readers
210 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Although a good guess, this looks more like the work of someone who's in way over their head and barely knows how to use git. Probably just downloaded the repo as a zip instead of cloning it through git. At least that's the vibe I get from their commit history and other repos.
So basically, this person did the right thing on accident.
FWIW, this can actually be a valid strategy, purely because a DMCA takedown will affect forks but not reuploads. Basically, if a DMCA takedown nukes a project, it also nukes any forked projects. But if you downloaded the .zip and reuploaded it, you won’t be affected by the DMCA takedown because it’s not considered a fork of the original project.
It’s a dumb workaround, but it oddly may have helped save a lot of the code simply because offline backups can’t get touched by DMCA or a nuked project.