Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
103 changes: 103 additions & 0 deletions 2026/07/2026-07-20-fluxroute.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,103 @@
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] [private] [private] and copyright holder of the project "FluxRoute" (https://github.com/klondike0x/FluxRoute). [private] created and [private] all the source code, and I have not authorized the use of [private] copyrighted work in the infringing repository. I am not acting on behalf of anyone else.

**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**

The original work is the "FluxRoute" project, a desktop application for managing network bypass strategies. It includes original source code, unique integration with TG WS Proxy via embedded Python with automatic dependency installation, and is licensed under GPLv3. The first commit was made on March 7, 2026, and the project is publicly available at https://github.com/klondike0x/FluxRoute.

**If the original work referenced above is available online, please provide a URL.**

https://github.com/klondike0x/FluxRoute

**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/mx57/BSDPI_AI

**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 infringing repository mx57/BSDPI_AI violates the GPLv3 license in the following ways:

1. Removal of copyright notice (GPLv3 §4(a)): [private] original LICENSE file contains "Copyright (c) 2026 klondike0x". This file was deleted and replaced with a NOTICE file containing "Copyright (C) 2026 mx57". This is a direct violation of GPLv3 §4(a), which requires that all copyright notices be preserved.

2. Failure to indicate modifications (GPLv3 §5(c)): The infringer has not marked modified files or provided any notice that changes were made to the original work.

3. False and misleading attribution (GPLv3 §7(e)): The infringer falsely claims in the README that his repository is the "parent" of all AI features, when in fact [private] original work predates his repository. [private] first commit was on March 7, 2026; his repository was created on March 10, 2026.

4. Unauthorized copying of complete source files without preserving attribution: The infringer copied entire files from [private] project, including unique method names like OnCustomScrollHandler and SetOpacity, which are [private] original creation and do not appear in any public library.

Additionally, the infringer copied [private] unique approach to TG WS Proxy integration using embedded Python with automatic cryptography installation, including the same file structure (tg-proxy/python/, tg-proxy/proxy/) and step-by-step implementation. This demonstrates that the entire project is a derivative work of [private] original code.

**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.**

To bring the infringing repository into full compliance with GPLv3, the following changes are required:

1. Restore the original copyright notice: The LICENSE file must be restored with the original copyright notice "Copyright (c) 2026 klondike0x" intact.

2. Remove the false NOTICE file: The NOTICE file that claims "Copyright (C) 2026 mx57" must be removed.

3. Clearly indicate modifications: The infringer must add a notice in each modified file stating that changes were made, as required by GPLv3 §5(c).

4. Remove false attribution claims: The false statement in README about being the "parent" of AI features must be corrected or removed.

5. Preserve all original copyright notices in the copied source files: All source files that were copied from [private] original project must include the original copyright notices.

6. Either: (a) Remove the infringing repository entirely, or (b) bring it into full compliance with GPLv3 as described above.

**Do you have the alleged infringer’s contact information? If so, please provide it.**

**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]