WT actual F??<p>From GitHub's policy on submitting a DMCA takedown notice[1] on what the complaint must contain:<p>> <i>(7) Include the following statement: "I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration."</i><p>> <i>(8) Also include the following statement: "I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed."</i><p>The claimed "<i>original content</i>" (preloaded programs for a fx-FD10 Pro) cited in the takedown notice[2] isn't even remotely relevant to the physical host that the hack targets (a fx-991MS). After watching the 11 min video and without even looking at the repo contents, it's so obvious that REACT couldn't possibly have submitted this DMCA takedown notice "<i>in good faith</i>" given the standalone hack has <i>absolutely nothing</i> to do with the target host's firmware/software--or anything published on Casio's website--to begin with!<p>So "<i>under penalty of perjury</i>", React is exploiting how GitHub passively handles these DMCA takedown notices...I mean seriously, an irrelevant download link that clearly wasn't reviewed by anything that constitutes human intelligence can nerf an entire repo?? Unfortunately, this has been the meta for as long as I can remember and this pragmatically non-existent qualifying bar is just 1 reason why I don't play on GitHub.<p>But the part I find to be the most egregious that it appears no one is really talking about? To defend himself, this guy has to satisfy GitHub's counter notice policy[3], in particular:<p>> <i>(3) Provide your contact information. Include your email address, name, telephone number, and physical address.</i><p>The policy doesn't even require explaining to GitHub why the takedown is bullshit; it's just to signal the other side that you're willing to defend the thing under scrutiny against further legal action. The guy already pulled the counter notice trigger, but without dedicated legal representation and/or the public media on your side, it's difficult for any 1 dood in the capacity of private citizen to expose personal identifiable information and embrace the threat of a legal harassment campaign by an organization of legal professionals. React knows they don't have anything, but if the victim doesn't have balls + legal counsel + disposable income, the gambit is that they really won't need anything either.<p>[1] <a href="https://help.github.com/en/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#your-complaint-must-" rel="nofollow">https://help.github.com/en/github/site-policy/guide-to-submi...</a><p>[2] <a href="https://github.com/github/dmca/blob/master/2020/05/2020-05-20-Casio.md" rel="nofollow">https://github.com/github/dmca/blob/master/2020/05/2020-05-2...</a><p>[3] <a href="https://help.github.com/en/github/site-policy/guide-to-submitting-a-dmca-counter-notice#your-counter-notice-must" rel="nofollow">https://help.github.com/en/github/site-policy/guide-to-submi...</a>