Skip to content

Commit a92ec8c

Browse files
Merge pull request #13122 from github/updates
Added 2023/03/2023-03-24-twitter.md
2 parents 2357f88 + aa3195a commit a92ec8c

File tree

1 file changed

+67
-0
lines changed

1 file changed

+67
-0
lines changed

2023/03/2023-03-24-twitter.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
2+
3+
Yes, I am authorized to act on the copyright owner's behalf.
4+
5+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
6+
7+
Yes
8+
9+
**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**
10+
11+
2074870
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 am a [private] on Twitter's [private]
20+
21+
**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.**
22+
23+
Proprietary source code for Twitter's platform and internal tools.
24+
25+
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
26+
27+
https://github.com/FreeSpeechEnthusiast/PublicSpace
28+
29+
**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.**
30+
31+
No
32+
33+
**<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.**
34+
35+
No
36+
37+
**Is the work licensed under an open source license?**
38+
39+
No
40+
41+
**What would be the best solution for the alleged infringement?**
42+
43+
Other Change
44+
45+
**Describe the change.**
46+
47+
Please preserve and provide copies of any related upload / download / access history (and any contact info, IP addresses, or other session info related to same), and any associated logs related to this repo or any forks thereof, before removing all the infringing content from Github.
48+
49+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
50+
51+
No
52+
53+
**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.**
54+
55+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
56+
57+
**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.**
58+
59+
**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>.**
60+
61+
**So that we can get back to you, please provide either your telephone number or physical address.**
62+
63+
Attn: [private], Twitter, [private]
64+
65+
**Please type your full legal name below to sign this request.**
66+
67+
[private]

0 commit comments

Comments
 (0)