├── 简体中文 └── 模板.md ├── 日本語 └── テンプレート.md ├── English ├── Template.md ├── nce3xin.md └── sinofine.md ├── README.zh_cn.md ├── LICENSE ├── README.ja_jp.md ├── README.md └── Sample.md /简体中文/模板.md: -------------------------------------------------------------------------------- 1 | > 你的其中一位被 996 工作制压迫的程序员把你站后台源码上传上了 GitHub。现在过了 2 小时，写一个邮件给 Github，描述现状，并请求 GitHub 把后台源码删了，以及你从这次经历中学到了什么。 2 | > 3 | > 修改这个模板的内容，开始撰写你的删除请求。撰写完毕后，修改这个文件名为“文章标题-你的用户名.md”，并提交 Pull Request！ 4 | > 5 | > （完成文章后，删除这一块内容） 6 | 7 | # 标题 8 | 9 | 正文从此开始... 10 | -------------------------------------------------------------------------------- /日本語/テンプレート.md: -------------------------------------------------------------------------------- 1 | > あなたの抑圧された996プログラムエンジニアのひとりがあなたのバックエンドのソースコードをGitHubにアップロードしました。 2時間が経過したので、GitHubにEメールを送り、状況を説明し、それを削除するようGitHubに依頼し、この経験から学んだことを説明します。 2 | > 3 | > このファイルを修正して、削除通知を書き始めます。 削除通知が完了したら、このファイルの名前を「タイトル-ユーザー名.md」に変更してから、プルリクエストを送信してください。 4 | > 5 | > (完了後にこれを削除) 6 | 7 | # Title 8 | 9 | ここから書き込みを始めます... 10 | -------------------------------------------------------------------------------- /English/Template.md: -------------------------------------------------------------------------------- 1 | > One of your oppressed 996 program engineers has uploaded your backend source code to GitHub. Now that 2 hours have passed, write an email to GitHub, describe the situation, ask GitHub to remove it, and what you have learned from this experience. 2 | > 3 | > Start writing your takedown notice by modifing this file. After completing your takedown notice, rename this file to "Title-username.md", then submit a pull request! 4 | > 5 | > (Remove this after completion) 6 | 7 | # Title 8 | 9 | Begin your writes from here... 10 | -------------------------------------------------------------------------------- /README.zh_cn.md: -------------------------------------------------------------------------------- 1 | # 请求依据 DMCA 删除 2 | 3 | :crossed_flags: 4 | [English][EN_US], 5 | **简体中文**, 6 | [日本語][JA_JP] 7 | 8 | 9 | [EN_US]:README.md 10 | [ZH_CN]:README.zh_cn.md 11 | [JA_JP]:README.ja_jp.md 12 | 13 | 我们要用我们自己的方法一起守护B站，帮B站给GitHub写一个更好的邮件！ 14 | 15 | ## 需求 16 | 17 | 你的其中一位被 996 工作制压迫的程序员把你站后台源码上传上了 GitHub。现在过了 2 小时，写一封邮件给 GitHub，描述现状，并请求 GitHub 把后台源码删了，以及你从这次经历中学到了什么。 18 | 19 | [原版(英)](Sample.md) 20 | 21 | ## 参与 22 | 23 | 1. Fork 24 | 2. 在对应语言的文件夹中新建一个文件，命名为你的名字 25 | 3. 根据以上要求写一封邮件 26 | 4. 发 pull request! 27 | 28 | ## 全部投稿 29 | 30 | 请投稿后在下面添加新链接 31 | 32 | 例如：[模板](简体中文/模板.md) 33 | 34 | [English/nce3xin.md](English/nce3xin.md) 35 | 36 | [English/sinofine.md](English/sinofine.md) 37 | 38 | ## 参考资料 39 | 40 | [DMCA删除政策(英)](https://help.github.com/en/articles/dmca-takedown-policy) 41 | 42 | [如何提交DMCA删除通告(英)](https://help.github.com/en/articles/guide-to-submitting-a-dmca-takedown-notice) 43 | 44 | [如何提交DMCA反通告(英)](https://help.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice) 45 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2019 closebilibili 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.ja_jp.md: -------------------------------------------------------------------------------- 1 | # DMCAによる削除 2 | 3 | :crossed_flags: 4 | [English][EN_US], 5 | [简体中文][ZH_CN], 6 | **日本語** 7 | 8 | 9 | [EN_US]:README.md 10 | [ZH_CN]:README.zh_cn.md 11 | [JA_JP]:README.ja_jp.md 12 | 13 | 私たちは自分なりのやり方でビリビリを守り、ビリビリを助けてより正しいメールを書きましょう。 14 | 15 | ## 必要条件 16 | 17 | 2時間前、ビリビリがあなたの一人の996に抑圧されたソフトウェアエンジニアの同僚にバックグラウンドソースコードをGitHubにアップロードされてしまいました。現在、あなたはこの厳しい状況を説明し、GitHubにアップロードされたコードを削除するように依頼し、自分がこの件から学んだ経験を述べるのに、GitHubにメールを書いてください。 18 | 19 | [原文(En)](Sample.md) 20 | 21 | ## 応募方法 22 | 23 | 1. このGithub RepositoryをForkします； 24 | 2. 相応の言語のフォルダに新たなファイルを設立し、自分の名前で命名します； 25 | 3. 上記の要件に従ってメールを書きます； 26 | 4. Pull Requestします。 27 | 28 | ## 応募後 29 | 応募した方はこの下にリンクを付けてください 30 | 31 | ＜例＞ 32 | * [日本語/テンプレート.md](日本語/テンプレート.md) 33 | * [English/nce3xin.md](English/nce3xin.md) 34 | * [English/sinofine.md](English/sinofine.md) 35 | 36 | ## 参考文献 37 | 38 | [DMCAテイクダウンポリシー(En)](https://help.github.com/en/articles/dmca-takedown-policy) 39 | 40 | [DMCAテイクダウン通知の送信ガイド(En)](https://help.github.com/en/articles/guide-to-submitting-a-dmca-takedown-notice) 41 | 42 | [DMCA異議申し立て通知を送信するためのガイド(En)](https://help.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice) 43 | -------------------------------------------------------------------------------- /English/nce3xin.md: -------------------------------------------------------------------------------- 1 | # DMCA Takedown Notice 2 | 3 | Hello GitHub, 4 | 5 | We are the team from [bilibili](https://www.bilibili.com/) company. A repository hosted on your site is infringing on copyrights owned by our company. 6 | 7 | Two hours ago, our company's backend source code was maliciously uploaded to a repository named 'openbilibili/go-common' without permission. This involves plenty of confidential information. Once revealed, it will strike a fatal blow to our company's website security. The unauthorized and infringing copy can be found at: 8 | 9 | [REPOSITORY URL] 10 | 11 | This letter is official notification under the Millennium Copyright Act ("DMCA"), and we seek the removal of the aforementioned infringing repository as well as all forks from your servers immediately to cease any further posting of infringing. 12 | 13 | We are providing this notice in good faith and with the reasonable belief that rights my company owns are being infringed. Under penalty of perjury we certify that the information contained in the notification is both true and accurate, and we have the authority to act on behalf of the owner of the copyright(s) involved. 14 | 15 | Should you wish to discuss this with us please contact us directly. 16 | 17 | Thank you. 18 | 19 | Address [private]\ 20 | City, State Zip [private]\ 21 | Phone [private]\ 22 | E-mail [private] 23 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # DMCA-takedown 2 | 3 | :crossed_flags: 4 | **English**, 5 | [简体中文][ZH_CN], 6 | [日本語][JA_JP] 7 | 8 | 9 | [EN_US]:README.md 10 | [ZH_CN]:README.zh_cn.md 11 | [JA_JP]:README.ja_jp.md 12 | 13 | For our loved Bilibili, let's make this world a better place by helping Bilibili write his email to GitHub! 14 | 15 | ## Requirements 16 | 17 | One of your oppressed 996 program engineers has uploaded your backend source code to GitHub. Now that 2 hours have passed, write an email to GitHub, describing the situation, ask GitHub to remove it, and what you have learned from this experience. 18 | 19 | [Original edition](Sample.md) 20 | 21 | ## Contribution 22 | 23 | 1. Fork 24 | 2. Create a new file with your name in one of the folders according to language. 25 | 3. Write an email based on the Requirements above 26 | 4. Send a pull request! 27 | 28 | ## All submissions 29 | 30 | Please attach your submission below 31 | 32 | For example: [Template](English/Template.md) 33 | 34 | [English/nce3xin.md](English/nce3xin.md) 35 | 36 | [English/sinofine.md](English/sinofine.md) 37 | 38 | ## Further reading 39 | 40 | [DMCA Takedown Policy](https://help.github.com/en/articles/dmca-takedown-policy) 41 | 42 | [Guide to Submitting a DMCA Takedown Notice](https://help.github.com/en/articles/guide-to-submitting-a-dmca-takedown-notice) 43 | 44 | [Guide to Submitting a DMCA Counter Notice](https://help.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice) 45 | -------------------------------------------------------------------------------- /Sample.md: -------------------------------------------------------------------------------- 1 | Hello Dear Github: 2 | 3 | We Are: 4 | 5 | Bilibili Security Group.It is nice to be able to yse Github such a professional and effcient platform,and mpw we have a need to be very hopefully able to get Github's support and resolution.I sent the mail yesterday and the mail attachments is the my signature!! 6 | 7 | We have read and understand GitHub's Guide to Filling a DMCA Notice 8 | 9 | Some one created a Repository called 'openbilibili/go-common' two hours ago and many people forked it or clone it and reupload the repository,which contained too much sensitive information,such as secret key,database address,very important api key and so on.If these information are found by other people in Github,our company will be left out of pocket. 10 | 11 | The following is Github's URL and Screenshots about this Repository: 12 | 13 | [private] 14 | 15 | Since the reupload repositories and the contains our company's important source code,algorithm and system configuration,,so we hope Giuhub as soon as possible to help us completely remove the reupload repositories and thank you very much 16 | 17 | The following is our contact information: 18 | 19 | - Company Name : Bilibili 20 | - My e-mail Address: [private] 21 | - Cellphone: [private] 22 | - Company Address: [private] 23 | - Website: https://www.bilibili.com/ 24 | 25 | 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. 26 | 27 | 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. 28 | 29 | 30 | Hoping for your response and thanks again. 31 | Please help us!!! 32 | 33 | -------------------------------------------------------------------------------- /English/sinofine.md: -------------------------------------------------------------------------------- 1 | [Private] 2 | 3 | Yangpu District 4 | 5 | Bilibili Inc. 6 | 7 | Github DMCA Agent 8 | 9 | 88 Colin P Kelly Jr St 10 | 11 | San Francisco, CA. 94107 12 | 13 | 23 April 2019 14 | 15 | Dear Sir/Madam 16 | 17 | I am a member of security team of Bilibili Inc, authorised to act on behalf of the copyright holder (Bilibili Inc). 18 | 19 | Having read and understood GitHub’s Guide to Filling a DMCA Notice, I sincerely request that you, the DMCA Agent, make a takedown to the repositories as they include copies of Bilibili's proprietary back-end code, as follows. 20 | 21 | https://github.com/dncmn/go-common_bilibi/ 22 | 23 | https://github.com/yqh231/go_backup/ 24 | 25 | https://github.com/Jason-1995/Test/ 26 | 27 | https://github.com/yongge666/bsite/ 28 | 29 | https://github.com/closelibilibi/closelibilibi/ 30 | 31 | https://github.com/dig-gold-development/vs-common/ 32 | 33 | https://github.com/hellocodehi/bilibili-code--leaked/ 34 | 35 | https://github.com/Poco-Ye/openbilibili/ 36 | 37 | https://github.com/JfGitHub31/God_Lucky/ 38 | 39 | https://github.com/swituo/no-openbilibili-decoder 40 | 41 | https://github.com/RichardAckerman/blbl-go-common 42 | 43 | https://github.com/swituo/no-openbilibili 44 | 45 | https://github.com/Light-of-Hers/go-common-1 46 | 47 | https://github.com/hflamsam/bilibili-go-common 48 | 49 | https://github.com/onyz4x/go-common 50 | 51 | https://github.com/Jovins/bili-backup-notgo 52 | 53 | https://github.com/FerricChloride/bili-backup-notgo 54 | 55 | https://github.com/R-reborn/bilibili-go-common 56 | 57 | https://github.com/ljf1239848066/bilibili-go-common 58 | 59 | https://github.com/R-reborn/bilibili-go-common 60 | 61 | https://github.com/Omooo/BiLiBiLi-Go_Common 62 | 63 | https://github.com/hflamsam/bilibili-go-common 64 | 65 | https://github.com/hzsbdq/bilibili-go-common 66 | 67 | https://github.com/artyhacker/bilibili-go-common 68 | 69 | https://github.com/donnytab/go-common 70 | 71 | https://github.com/dongchenglong/go-common 72 | 73 | https://github.com/sensejoy/go-common 74 | 75 | https://github.com/zq56002718/go_common 76 | 77 | https://github.com/judebues/go-common 78 | 79 | https://github.com/legoming/Bilibili-Go-Backup 80 | 81 | https://github.com/harjeb/open-bilibili-backup 82 | 83 | https://github.com/myslule/bilibili-backend-source-backup 84 | 85 | https://github.com/dyrdro/backup-bilibili-source-go 86 | 87 | https://github.com/Azimiao/bilibili-backup-b 88 | 89 | https://github.com/liuhuanqiang/bilibili-backup-1 90 | 91 | https://github.com/seanpan565/bili 92 | 93 | https://github.com/yhan219/bilibili 94 | 95 | https://github.com/sevenelevenlee/go-common-bilibili 96 | 97 | https://github.com/dongmingming/go-common-release 98 | 99 | https://github.com/paoupup/bilibili-code--leaked 100 | 101 | https://github.com/HZZformGD/bilibili-common 102 | 103 | https://github.com/plusmultiply0/bilibili-common 104 | 105 | https://github.com/MrVoler/bilibili_code_study 106 | 107 | https://github.com/dongmingming/go-common-release 108 | 109 | [private] 110 | 111 | https://github.com/yWX225600/go_clicli 112 | 113 | https://github.com/wangwc1022/bilibili-study 114 | 115 | According to the requirements in the Guide to Submitting DMCA Take Down Notice, I render the statements as below: 116 | 117 | 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. 118 | 119 | 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. 120 | 121 | Yours faithfully 122 | 123 | [private] --------------------------------------------------------------------------------