Skip to content

Commit 0d8fe91

Browse files
Merge pull request #12694 from github/updates
Added 2023/01/2023-01-06-lirium.md
2 parents bcb61a7 + 1b2b45d commit 0d8fe91

File tree

1 file changed

+89
-0
lines changed

1 file changed

+89
-0
lines changed

2023/01/2023-01-06-lirium.md

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
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+
While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s).
10+
11+
---
12+
13+
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
14+
15+
Yes, I am the copyright holder.
16+
17+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
18+
19+
No
20+
21+
**Does your claim involve content on GitHub or npm.js?**
22+
23+
GitHub
24+
25+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
26+
27+
I am the [private] of this program, [private] [private] can be found online on the haze.yt/lirium website.
28+
So its my product and my copyright
29+
30+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
31+
32+
Its an jar file called Lirium, its buyable at https://haze.yt/lirium/
33+
34+
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
35+
36+
https://github.com/Endemic1337/Client-Archive/blob/main/Lirium/Lirium%20v1.4/Lirium%20v1.jar
37+
38+
**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.**
39+
40+
Yes
41+
42+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
43+
44+
We have an authorization system, obfuscation and an custom jvm so its harder too crack
45+
46+
**How is the accused project designed to circumvent your technological protection measures?**
47+
48+
Its has been reversed by an tool which isn't public.
49+
So he removed the authorization of the program.
50+
51+
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
52+
53+
There are no forks
54+
55+
**Is the work licensed under an open source license?**
56+
57+
No
58+
59+
**What would be the best solution for the alleged infringement?**
60+
61+
Other Change
62+
63+
**Describe the change.**
64+
65+
Takedown of the repository and some informations to sue him.
66+
67+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
68+
69+
Just his Github name and [private] account.
70+
71+
Github name: Endemic1337
72+
[private]: [private]
73+
74+
**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.**
75+
76+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
77+
78+
**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.**
79+
80+
**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>.**
81+
82+
**So that we can get back to you, please provide either your telephone number or physical address.**
83+
84+
Telephone number: [private]
85+
Address: [private]
86+
87+
**Please type your full legal name below to sign this request.**
88+
89+
[private]

0 commit comments

Comments
 (0)