Skip to content

Commit 330f659

Browse files
Merge pull request #13123 from github/updates
Added 2023/03/2023-03-23-mazorca.md
2 parents a92ec8c + de11907 commit 330f659

File tree

1 file changed

+74
-0
lines changed

1 file changed

+74
-0
lines changed

2023/03/2023-03-23-mazorca.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
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).
2+
3+
---
4+
5+
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
6+
7+
Yes, I am authorized to act on the copyright owner's behalf.
8+
9+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
10+
11+
No
12+
13+
**Does your claim involve content on GitHub or npm.js?**
14+
15+
GitHub
16+
17+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
18+
19+
I work in a company that owns the code in the specified repository. I am an [private] and I received instructions from my [private] to claim the code takedown.
20+
21+
22+
**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.**
23+
24+
The code is from our web site , hosted on https://mazorca.mx/ published last year.
25+
26+
27+
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
28+
29+
The entire repository https://github.com/S4dow/FUMO- (https://github.com/S4dow/FUMO-.git).
30+
31+
**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.**
32+
33+
Yes
34+
35+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
36+
37+
We added a code segment that blocks access to the web site copiers like HTTrack
38+
39+
40+
**How is the accused project designed to circumvent your technological protection measures?**
41+
42+
Before this attack our website wasn't protected.
43+
44+
**<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.**
45+
46+
There's not any fork
47+
48+
**Is the work licensed under an open source license?**
49+
50+
No
51+
52+
**What would be the best solution for the alleged infringement?**
53+
54+
Reported content must be removed
55+
56+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
57+
58+
No
59+
60+
**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.**
61+
62+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
63+
64+
**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.**
65+
66+
**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>.**
67+
68+
**So that we can get back to you, please provide either your telephone number or physical address.**
69+
70+
[private]
71+
72+
**Please type your full legal name below to sign this request.**
73+
74+
[private]

0 commit comments

Comments
 (0)