Skip to content

Commit 44fb1c9

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent b3f0b0e commit 44fb1c9

File tree

1 file changed

+50
-0
lines changed

1 file changed

+50
-0
lines changed

2025/12/2025-12-04-lua-script.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
Are you the copyright holder or authorized to act on the copyright owner's behalf?
2+
Yes, I am the copyright holder.
3+
4+
Are you submitting a revised DMCA notice after GitHub Trust & Safety requested changes?
5+
Yes.
6+
7+
Does your claim involve content on GitHub or npm.js?
8+
GitHub.
9+
10+
Please describe the nature of your copyright ownership or authorization.
11+
I am the [private] and exclusive copyright holder of the Lua scripts contained in [private] original private repository. The repository was private and the code was written entirely by [private]. The infringing repository contains unauthorized copies of [private] copyrighted work.
12+
13+
Please provide a detailed description of the original copyrighted work that has allegedly been infringed.
14+
The original copyrighted work consists of a collection of Lua scripts [private] authored. These scripts were stored in a private [private] repository that [private] own. The infringing repository contains unauthorized copies of [private] copyrighted work. Additionally, the infringer impersonated [private] and published the repository without [private] consent.
15+
16+
If the original work is available online, please provide a URL.
17+
The original work is not publicly available; it resided in a private git repository and was eventually published under [private] account.
18+
19+
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. Please clearly state that the entire repository is infringing OR list specific files.
20+
The entire repository is infringing.
21+
22+
Identify the full repository URL that is infringing:
23+
https://github.com/goose-birb/lua-buffoonery
24+
25+
Do you claim to have any technological measures in place to control access to your copyrighted content?
26+
No.
27+
28+
If you are reporting an infringing fork, list all fork URLs here:
29+
None.
30+
31+
Is the work licensed under an open source license?
32+
No.
33+
34+
What would be the best solution for the alleged infringement?
35+
The reported content must be removed.
36+
37+
Do you have the alleged infringer's contact information?
38+
I do not have the infringer’s contact information. The user had committed code under an unreachable email address.
39+
40+
I have a good-faith belief that the use of the copyrighted materials described above is not authorized by the copyright owner, its agent, or the law.
41+
42+
The original work was later published by [private] under a CC BY license on [private] own [private] account. However, the infringing repository predates [private] publication and was created without [private] permission. At the time the infringing repository was uploaded, [private] did not have a [private] account, and the infringer impersonated [private] and uploaded [private] private code without authorization. The infringing work was not published with any disclaimer, indication, or notice that it was intended as an educational tool. The infringer had no authorized access to the code prior to its legitimate publication, and therefore the infringing repository was never licensed or permitted.
43+
44+
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.
45+
46+
So that we can get back to you, please provide either your telephone number or physical address.
47+
[private]
48+
49+
Please type your full name for your signature.
50+
[private]

0 commit comments

Comments
 (0)