Skip to content

Commit cf44390

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent 270b56b commit cf44390

1 file changed

Lines changed: 121 additions & 0 deletions

File tree

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
**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.**
2+
3+
Yes, I am the copyright holder.
4+
5+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
6+
7+
No
8+
9+
**Does your claim involve content on GitHub or npm.js?**
10+
11+
GitHub
12+
13+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
14+
15+
"I have read and understand GitHub's Guide to Filing a DMCA Notice."
16+
17+
"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 fair use into consideration."
18+
19+
"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."
20+
21+
[private]
22+
[private]
23+
[private]
24+
[private]
25+
[private]
26+
TEL: [private]
27+
28+
ATTACHED CONTACT DETAILS OF THE COPYRIGHT INFRINGER & SOFTWARE THIEF + ATTACHED PROOF.
29+
30+
Hi,
31+
32+
You're a thief, [private].
33+
34+
I would like to report this profile of this individual ([private]) - as well as several links to specific posts - who has stolen [private] software, TorahBibleCodes, and developed software based upon [private] software, and is using it in violation of the copyright (ALL RIGHTS RESERVED by DEFAULT because NO LICENSE WAS GIVEN) for not only public use, but also for commercial use (ATTACHED PROOF).
35+
36+
He then used this software to sell digital prints & hard-copy prints of Bible Code searches.
37+
38+
I learned of his software today when a user contacted [private] inquiring about a bible code search using the software.
39+
40+
[private] then contacted the developer of this software and thanked him for the "passing mention" of attribution of the original software on which it is based, but asked him (as a courtesy even though [private] do not have to allow him to continue to allow public use) to simply to: 1.) place the attribution at the top of the GitHub page as well at the bottom footer of the app he developed ON [private] BACK, and 2.) reminded him that since there is no license given on GitHub, that the default license is ALL RIGHTS RESERVED and reiterated that commercial use is prohibited, and specified that use is free only for free, private, educational use only.
41+
42+
He agreed to [private] requests, but within a few minutes [private] found that he was using this software for commercial purposes and selling for profit digital and hard-copy prints.
43+
44+
When [private] asked him if he had profited from this, [private] mentioned he needed to pay [private] 1/2 of the profit (although [private] could demand 100% by law).
45+
46+
He then said he did not make any money - so [private] rephrased [private] question to ask if anybody had made any money.
47+
48+
It turns out that the site that he was selling these on belongs to him.
49+
50+
He later replied that he would not agree to any of the requests, and claimed that he never agreed to [private] previous requests - and instead of attributing to [private] software, he decided to remove all mention of [private] software, and claim that the software is original (even though in screen shots you can see that he mentions [private] as the original developer as well as that he forked the software and developed enhancements).
51+
52+
I would like his posts removed as well as his profile deleted for violating terms of [private] by engaging in willful violation of copyright, copyright infringement, and theft of [private] software (without shame).
53+
54+
[private]
55+
56+
Thank you very much.
57+
58+
Best regards,
59+
[private]
60+
[private]
61+
[private]
62+
63+
#################################################################
64+
CONTACT DETAILS OF COPYRIGHT INFRINGER + SOFTWARE THIEF
65+
66+
[private]
67+
68+
69+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
70+
71+
[private]
72+
73+
I have screenshots of the violations, his agreement to comply with [private] requests for clear attribution + no commercial use, then his later e-mail saying that he never agreed, screenshots, PDFs of our e-mail correspondence. I will send all these via e-mail to [private]
74+
75+
**If the original work referenced above is available online, please provide a URL.**
76+
77+
[private]
78+
79+
**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.**
80+
81+
**Based on the above, I confirm that:**
82+
83+
The entire repository is infringing
84+
85+
**Identify the full repository URL that is infringing:**
86+
87+
[private]
88+
89+
**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.**
90+
91+
No
92+
93+
**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:**
94+
95+
**Is the work licensed under an open source license?**
96+
97+
No
98+
99+
**What would be the best solution for the alleged infringement?**
100+
101+
Reported content must be removed
102+
103+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
104+
105+
[private]
106+
107+
**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.**
108+
109+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
110+
111+
**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.**
112+
113+
**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>.**
114+
115+
**So that we can get back to you, please provide either your telephone number or physical address.**
116+
117+
[private]
118+
119+
**Please type your full name for your signature.**
120+
121+
[private]

0 commit comments

Comments
 (0)