OP should then just claim it as his own 😁
Comment on I got a DMCA notice for having a fork of GPL 3.0 code
pewpew@feddit.it 3 weeks ago
According to Github’s TOS you have the right to fork a repository (docs.github.com/en/…/github-terms-of-service#5-li…). So when they went closed source they removed the original repository to make it look like you stole their source code… That’s incredibly scummy
Valmond@lemmy.dbzer0.com 3 weeks ago
Grntrenchman@lemmy.world 3 weeks ago
That’s the power of GitHub. The fork still shows idolize as the author and clearly has gpl3 license (added by idolize). They can change what they want in the original repo, but the fork is covered forever, and ironclad proof of the licensing. If OP’s code is based off this fork, unmodified (of which it’s a fork, also ironclad proof it’s that gpl3 version) then it’s also gpl3. Saaaafe. This should be open and shut on github’s end, just a dumb DMCA report.
mkwt@lemmy.world 3 weeks ago
OP needs to counter-notice this shit.
Thedogdrinkscoffee@lemmy.ca 3 weeks ago
Better yet not use git-hub. Opression tech is nobody’s friend.
InFerNo@lemmy.ml 3 weeks ago
The power of github is discoverability. Projects on other platforms might as well not exist to a lot of people.
WhyJiffie@sh.itjust.works 3 weeks ago
the commiter name in the repo is not ironclad proof, anyone can upload commits to their repo in Linus Torvalds’ name. but github probably has the capabilities to find out who was the original uploader of the commit, or what was the upstream repo of a fork
Appoxo@lemmy.dbzer0.com 3 weeks ago
What if it is signed?
WhyJiffie@sh.itjust.works 3 weeks ago
if it is signed by a key used in public repos of the commiter, or otherwise known to possess the key, that is proof, yes
WhyJiffie@sh.itjust.works 3 weeks ago
if it is signed by a key used in public repos of the commiter, or otherwise known to possess the key, that is proof, yes