From ddef0f2ef6ecc7afe91d73bbd9458683af415015 Mon Sep 17 00:00:00 2001 From: dmca-sync-bot Date: Thu, 9 Jun 2022 18:03:25 +0000 Subject: [PATCH] Process DMCA request --- 2022/06/2022-06-08-wuba.md | 74 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) create mode 100644 2022/06/2022-06-08-wuba.md diff --git a/2022/06/2022-06-08-wuba.md b/2022/06/2022-06-08-wuba.md new file mode 100644 index 000000000..653c48896 --- /dev/null +++ b/2022/06/2022-06-08-wuba.md @@ -0,0 +1,74 @@ +Before disabling any content in relation to this takedown notice, GitHub +- 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). +- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice). + +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). + +--- + +**Are you the copyright holder or authorized to act on the copyright owner's behalf?** + +Yes, I am the copyright holder. + +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** + +No + +**Does your claim involve content on GitHub or npm.js?** + +GitHub + +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** + +I work for the WUBA(58) company and the owner of corresponding internal project. An introduction to WUBA(58) can be found in this address: https://zh.wikipedia.org/zh-hk/58%E5%90%8C%E5%9F%8E#%E4%B8%BB%E8%A6%81%E8%B3%87%E7%94%A2 + +**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.** + +https://github.com/Binvy/green-handbook/tree/161202a97bcc9f53db2cf65081a3d853e04289d3/notes/work this commit,not only contains WUBA company internal code,but also contains WUBA Sensitive information. +for the internal code,ALL code in this commit and dictionary should not be published.For example, https://github.com/Binvy/green-handbook/blob/161202a97bcc9f53db2cf65081a3d853e04289d3/notes/work/MailUtil.java, This is the part of the code of WUBA Company mail system.https://github.com/Binvy/green-handbook/blob/161202a97bcc9f53db2cf65081a3d853e04289d3/notes/work/%E5%B7%A5%E4%BD%9C%E6%97%A5%E5%BF%97, one of its part is the code for The operation and maintenance personnel view the alarm information,it started at the line 352f of the file. +for the Sensitive information,ALL of the file except code file contains the Sensitive information.eg:https://github.com/Binvy/green-handbook/blob/161202a97bcc9f53db2cf65081a3d853e04289d3/notes/work/9%E6%9C%88%E4%BB%BD%E8%A1%A5%E5%85%85iMei%E5%8F%B7%E6%9C%AA%E6%88%90%E5%8A%9F%E7%9A%84%E5%87%BA%E5%BA%93%E5%95%86%E5%93%81%E4%BF%A1%E6%81%AF, contains Product information that is not out of stock of WUBA company,This should not be published because it is related to the order information. +also eg:https://github.com/Binvy/green-handbook/blob/161202a97bcc9f53db2cf65081a3d853e04289d3/notes/work/%E5%B7%A5%E4%BD%9C%E6%97%A5%E5%BF%97,c ontains the Server warning information of WUBA company in Chinese +There are many places that can confirm that those files are belong to WUBA company.This word "zhuanzhuan",appears frequently in those files,and zhuanzhuan is a product of WUBA company.one of its site is https://www.zhuanzhuan.com/ +so https://github.com/Binvy/green-handbook/tree/161202a97bcc9f53db2cf65081a3d853e04289d3/notes/work + ,should not be authorized to be in the public domain. + +**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.** + +the dictionary in this commit:https://github.com/Binvy/green-handbook/tree/161202a97bcc9f53db2cf65081a3d853e04289d3/notes/work + +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** + +No + +**Have you searched for any forks 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.** + +we found no forks + +**Is the work licensed under an open source license?** + +No + +**What would be the best solution for the alleged infringement?** + +Repository can be made private + +**Do you have the alleged infringer’s contact information? If so, please provide it.** + +No. We tried our best to find contact details but could not get them + +**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.** + +**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.** + +**I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.** + +**So that we can get back to you, please provide either your telephone number or physical address.** + +phone: [private] +address: [private] + +**Please type your full legal name below to sign this request.** + +[private]