Skip to content

Commit 0efcf43

Browse files
Merge pull request #21048 from github/updates
Added 2026/06/2026-06-30-voip-go-library.md
2 parents 6d34939 + 987d9b2 commit 0efcf43

1 file changed

Lines changed: 83 additions & 0 deletions

File tree

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
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+
**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.**
10+
11+
Yes, I am the copyright holder.
12+
13+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
14+
15+
No
16+
17+
**Does your claim involve content on GitHub or npm.js?**
18+
19+
GitHub
20+
21+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
22+
23+
I [private] the code and [private] it under [private] [private] repo on GitHub using [private] [private] and [private] [private] license.
24+
25+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
26+
27+
A GO library that provides for WA Web VOIP capabilities.
28+
29+
**If the original work referenced above is available online, please provide a URL.**
30+
31+
https://github.com/purpshell/meowcaller
32+
33+
**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.**
34+
35+
**Based on the above, I confirm that:**
36+
37+
Specific files within the repository are infringing
38+
39+
**Identify only the specific file URLs within the repository that is infringing:**
40+
41+
https://github.com/nocodeleaks/quepasa/tree/main/src/voip/calls and any file under this directory
42+
43+
**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.**
44+
45+
No
46+
47+
**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:**
48+
49+
**Is the work licensed under an open source license?**
50+
51+
Yes
52+
53+
**Which license?**
54+
55+
mit-license
56+
57+
**How do you believe the license is being violated?**
58+
59+
By the license file not being included or any credit being given or mentioned.
60+
61+
**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.**
62+
63+
adding attribution, adding a license
64+
65+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
66+
67+
No contact.
68+
69+
**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.**
70+
71+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
72+
73+
**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.**
74+
75+
**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>.**
76+
77+
**So that we can get back to you, please provide either your telephone number or physical address.**
78+
79+
[private]
80+
81+
**Please type your full name for your signature.**
82+
83+
[private]

0 commit comments

Comments
 (0)