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
118 changes: 118 additions & 0 deletions 2026/08/2026-08-25-archivetune.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,118 @@
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?**

Yes

**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**

4323032

**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 copyright holder of the ArchiveTune project, publicly available at https://github.com/ArchiveTuneApp/ArchiveTune.

All relevant source code, including the affected files, was written and published by [private] under the GPL-3.0 license. [private] have not transferred or assigned [private] copyright to any third party.

I am submitting this notice on [private] own behalf as the [private] copyright holder of the entire copied or derived repository content.

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

The copyrighted work is a software project titled “ArchiveTune,” which [private] created and maintain. The original work is publicly available at:

https://github.com/ArchiveTuneApp/ArchiveTune

ArchiveTune is an original software application consisting of source code written by [private], including Kotlin application code, user interface implementation, media-related functionality, project structure, and supporting logic.

The copyrighted work involved in this claim includes the ArchiveTune source code repository as a whole, including files located under the application source tree, such as:

https://github.com/ArchiveTuneApp/ArchiveTune/tree/main/app/src/main/kotlin/moe/rukamori/archivetune

The work includes original code structure, implementation logic, file organization, naming, and source-level expression that are identifiable in the repository. This code was independently created and published by me under the GNU General Public License v3.0 (GPL-3.0).

The GitHub repository above is the canonical public source and publication record for the ArchiveTune project.

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

https://github.com/ArchiveTuneApp/ArchiveTune
https://github.com/ArchiveTuneApp/ArchiveTune/tree/main/app/src/main/kotlin/moe/rukamori/archivetune

**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/Arturo254/OpenTune

**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 is using code from [private] project (ArchiveTune, licensed under GPL-3.0) without complying with the license terms.

Specifically, original source files from [private] project have been copied or derived, but the original copyright notices have been removed and replaced with different attribution. The infringing files do not retain [private] copyright notice, do not acknowledge that the work is derived from ArchiveTune, and do not indicate that modifications were made.

Under GPL-3.0, redistributors are required to preserve copyright notices and provide proper attribution. By removing these notices and presenting the code as their own original work, the repository violates the license terms.

Because these conditions have not been met, the use and distribution of [private] code is not authorized under the GPL-3.0 license.

**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 can be brought into compliance with the GPL-3.0 license by restoring the original copyright notices in all affected source files and clearly attributing the work to the ArchiveTune project.

Specifically, the repository must:
- Reintroduce the original copyright notices identifying [private] as the author
- Clearly indicate that the affected files are derived from the ArchiveTune project
- Retain the GPL-3.0 license and include proper attribution in the repository

Alternatively, if the repository owner does not wish to comply with these requirements, the infringing content should be removed.

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

GitHub username: Arturo254
Repository: https://github.com/Arturo254/OpenTune

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