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
90 changes: 90 additions & 0 deletions 2026/07/2026-07-29-dumbware.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
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 authorized to act on the copyright owner's behalf.

**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 submitted an earlier notice regarding the account then known as "[private]" several weeks ago, which received no response or action from GitHub. This is a new submission, not a revision requested by GitHub. Note: the account "[private]" has since been renamed to "studio2201" (GitHub's own API confirms these are the same underlying account/repositories — requests for the former owner name redirect to the current one), and the infringing content remains live and has continued to be actively updated since that earlier report.

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

"DumbWare" suite of self-hosted, open-source web applications, published under the GNU General Public License v3.0 (GPLv3) at [private]
**If the original work referenced above is available online, please provide a URL.**

https://github.com/DumbWareio/DumbWhoIs
https://github.com/DumbWareio/DumbDo
https://github.com/DumbWareio/DumbPad
https://github.com/DumbWareio/DumbKan
https://github.com/DumbWareio/DumbDrop

**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/studio2201/trace
https://github.com/studio2201/todo
https://github.com/studio2201/pad
https://github.com/studio2201/grid
https://github.com/studio2201/beam

**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 GPLv3 requires that any distributed derivative work also be licensed under GPLv3 (or a compatible copyleft license), that the original copyright notices be preserved, and that any modifications be documented. The repositories listed above (studio2201/trace, todo, pad, grid, beam) are derivative reimplementations GPLv3-licensed DumbWare applications — matching their specific feature sets and non-obvious implementation choices (e.g., identical third-party API fallback chains and ordering, identical result-display structure) — but are published under the permissive Apache-2.0 license instead, with no attribution to the original DumbWare projects or their GPLv3 licensing, and no notice of modifications. This strips users of the copyleft protections and attribution rights guaranteed by the GPLv3.

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

Relicense all five repositories under GPLv3 (or a GPLv3-compatible license), add clear attribution to the original DumbWare projects ([private]) with copyright notices restored, and add a notice documenting what was changed from the original source. Alternatively, remove the repositories/content entirely.

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

GitHub account: studio2201 (organization), formerly operating under the username [private] — same underlying account/repositories per GitHub's own redirect behavior. No other contact information is known.

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