Merge pull request #20314 from github/updates

Added 2026/04/2026-04-08-video-compression-code.md

Author: dmca-sync-bot

2026/04/2026-04-08-video-compression-code.md

@@ -0,0 +1,85 @@
+Before disabling any content in relation to this takedown notice, GitHub
+- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).
+- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
+
+To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.**
+
+Yes, I am the copyright holder.
+
+**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
+
+No
+
+**Does your claim involve content on GitHub or npm.js?**
+
+GitHub
+
+**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
+
+I am the [private] and [private] of the Tiktok-60Fps-compression-beypasser
+code.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+A browser extension namedTiktok-60Fps-compression-beypasser that bypass video compression. the infringer took the original source code and just changed the branding while NOT mentioning and giving PROPER credits. proof of infringement is that his code matches mine in bot logic and even html design adding a password to lock the features and even setting up a paywall to access infringed encrypted work of [private] [private] main proof is him forgetting to remove [private] name from the read me files and [private] own watermark in the code but he completly beypasses it instead of removing it
+
+**If the original work referenced above is available online, please provide a URL.**
+
+https://github.com/XYETHER/Tiktok-60Fps-compression-beypasser
+
+**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.**
+
+**Based on the above, I confirm that:**
+
+The entire repository is infringing
+
+**Identify the full repository URL that is infringing:**
+
+https://github.com/gaynalgaynal0-afk/JV_60FPS
+
+**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
+
+No
+
+**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:**
+
+**Is the work licensed under an open source license?**
+
+Yes
+
+**Which license?**
+
+gnu-general-public-license-v3.0
+
+**How do you believe the license is being violated?**
+
+The user copied [private] entire source code but violated the GPLv3 license by failing to provide attribution and falsely claiming it as their own work. They modified the branding, added a password to lock features, and set up a paywall to monetize [private] code. The codebase contains identical logic and HTML design. Furthermore, the infringer failed to fully remove [private] original name from the README files and left [private] original watermark embedded in the code, which they attempted to bypass rather than remove.
+
+**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.**
+
+The repository must be entirely removed. To bring it into compliance with GPLv3, the user would need to fully restore [private] original copyright notices, explicitly credit [private] as the original creator, and remove the paywall/encryption to provide the modified source code openly under the GPLv3 license. Because the work is blatantly stolen and monetized, I request immediate removal.
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+[private] id : [private]  
+[private] : [private]
+
+**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 <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
+
+**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 have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
+
+**So that we can get back to you, please provide either your telephone number or physical address.**
+
+[private]
+
+**Please type your full name for your signature.**
+
+[private]