Skip to content

Commit e35fcaf

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent 7cabd2d commit e35fcaf

File tree

1 file changed

+146
-0
lines changed

1 file changed

+146
-0
lines changed
Lines changed: 146 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,146 @@
1+
Before disabling any content in relation to this takedown notice, GitHub
2+
- 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).
3+
- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
4+
5+
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).
6+
7+
---
8+
9+
**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.**
10+
11+
Yes, I am the copyright holder.
12+
13+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
14+
15+
No
16+
17+
**Does your claim involve content on GitHub or npm.js?**
18+
19+
GitHub
20+
21+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
22+
23+
I am [private], the original [private] and copyright owner
24+
of the "A1Evo 1-click Optimization Tool" (also known as "A1 Evo Maestro MJ").
25+
26+
[private] created and first published this work in June 2024, with the most recent
27+
version published on September 10, 2024. The original work was published publicly on
28+
[private] [private] at: [private]
29+
30+
I am the copyright owner of this original HTML/JavaScript application and hold
31+
all exclusive rights to the work. [private] published this work under an MIT-based
32+
license with commercial restrictions that explicitly require:
33+
34+
"The above copyright notice and this permission notice shall be included in
35+
all copies or substantial portions of the Software."
36+
37+
The original copyright notice clearly states:
38+
"Copyright (c) [Jun 2024] [private]"
39+
40+
This is verifiable through [private] [private] channel (@[private]) where [private] published
41+
instructional content explaining this tool's usage, which predates the infringing
42+
repository.
43+
44+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
45+
46+
[private] original copyrighted work is a sophisticated HTML/JavaScript application
47+
titled "A1 Evo Maestro MJ.html" - a room correction optimization
48+
script tool designed for audio enthusiasts using Audyssey calibration systems.
49+
50+
**Key Technical Features & Distinctive Elements:**
51+
52+
1. **Unique Algorithm & Functionality**: The application implements a proprietary
53+
optimization workflow that processes Audyssey calibration files (.ady format)
54+
by integrating with Room EQ Wizard's API to generate parametric EQ
55+
recommendations for home theater systems.
56+
57+
2. **Distinctive Code Architecture**: The work contains several hundred lines of
58+
original JavaScript including:
59+
- Custom filter management system with dynamic parametric EQ tables
60+
- Advanced speaker channel detection arrays (modelsSoS300, micCalProb, noxo180)
61+
- Proprietary REW API fetching functions (postDelete, postNext, postAlign, fetchSafe etc.)
62+
63+
3. **Specific Functional Components**:
64+
- File upload system for .ady calibration file parsing
65+
- Integrated REW API client ([private])
66+
- Multi-speaker optimization with individual PEQ filter chains
67+
- Progress logging system with color-coded output (warnings, errors, info, logs)
68+
69+
The work represents approximately 1,300+ lines of original HTML/CSS/JavaScript
70+
code developed over multiple versions (original June 2024 through September 2024
71+
updates).
72+
73+
**If the original work referenced above is available online, please provide a URL.**
74+
75+
The original copyrighted work is available at:
76+
77+
Primary URL: [private]
78+
Published: September 10, 2024 (with original creation in June 2024)
79+
80+
Supporting Evidence of Prior Authorship:
81+
- [private] Channel: [private] (contains instructional
82+
video explaining the tool's usage and features, predating the infringing work - 07 June 2024 - https://youtu.be/lmZ5yV1-wMI)
83+
- Copyright notice in original: "Copyright (c) [Jun 2024] [[private]]"
84+
85+
The infringing work was published by navid0308 between 2025-2026 (as stated in
86+
their copyright notice), making it at minimum 6+ months after the original
87+
publication date.
88+
89+
**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.**
90+
91+
**Based on the above, I confirm that:**
92+
93+
The entire repository is infringing
94+
95+
**Identify the full repository URL that is infringing:**
96+
97+
https://github.com/navid0308/A1Evo_MJ_Custom
98+
99+
**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.**
100+
101+
No
102+
103+
**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:**
104+
105+
**Is the work licensed under an open source license?**
106+
107+
Yes
108+
109+
**Which license?**
110+
111+
mit-license
112+
113+
**How do you believe the license is being violated?**
114+
115+
The MIT license requires: "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."
116+
117+
The infringing work replaced [private] original copyright notice with their own (2025-2026 navid0308), violating the mandatory attribution requirement. Additionally, [private] license prohibits commercial use without permission—they are republishing as their own work.
118+
119+
**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.**
120+
121+
Restore original copyright notice in the HTML file header with [private] name and June 2024 date
122+
Include full license text with commercial restrictions clause
123+
Link to original source ([private])
124+
Alternatively: Make the repository private or delete the infringing files.
125+
126+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
127+
128+
GitHub Username: navid0308
129+
GitHub Profile: [private]
130+
Repository: https://github.com/navid0308/A1Evo_MJ_Custom
131+
132+
**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.**
133+
134+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
135+
136+
**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.**
137+
138+
**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>.**
139+
140+
**So that we can get back to you, please provide either your telephone number or physical address.**
141+
142+
[private]
143+
144+
**Please type your full name for your signature.**
145+
146+
[private]

0 commit comments

Comments
 (0)