-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Added 2026/04/2026-04-08-taoyuan.md #20307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,97 @@ | ||||||||||||||||||||||
| 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? 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.** | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| 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 am the [private] [private] and copyright holder of the original work. [private] created the entire codebase, game design, and all associated creative content [private], and published it under [private] [private] account ([private]) on February 7, 2026. | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| **Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| The original work is "桃源乡 (Taoyuan)", a browser-based text-driven farming simulation game written in Vue 3.5 + TypeScript. The work includes original source code, game design data (38 crop types, 19 animal species, 60 fish species, 120 mine levels, 34 NPCs, 113 recipes, 109 achievements, 28-day season cycle), UI design system (color palette #1a1a1a/#c8a45c, zpix pixel font, 768px responsive breakpoint), and all creative content. | ||||||||||||||||||||||
| | ||||||||||||||||||||||
| The allegedly infringing repository (https://github.com/bygas/gaKoy) is a direct copy of [private] work. The infringing party originally forked [private] repository, then removed the fork relationship and re-published it as an independent repository to conceal the origin. The infringing repository: | ||||||||||||||||||||||
| | ||||||||||||||||||||||
|
Comment on lines
+28
to
+30
|
||||||||||||||||||||||
| The allegedly infringing repository (https://github.com/bygas/gaKoy) is a direct copy of [private] work. The infringing party originally forked [private] repository, then removed the fork relationship and re-published it as an independent repository to conceal the origin. The infringing repository: | |
| The allegedly infringing repository (https://github.com/bygas/gaKoy) is a direct copy of [private] work. The infringing party originally forked [private] repository, then removed the fork relationship and re-published it as an independent repository to conceal the origin. The infringing repository: |
Copilot
AI
Apr 15, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The notice indicates the work is under an “open source license” but later references CC BY-NC 4.0, which is generally not considered an open-source license due to the non-commercial restriction. If this is meant to be internally consistent, update either the open-source answer or the license selection to match the intended classification.
| Yes | |
| **Which license?** | |
| other | |
| No | |
| **Which license?** | |
| CC BY-NC 4.0 |
Copilot
AI
Apr 15, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The notice indicates the work is under an “open source license” but later references CC BY-NC 4.0, which is generally not considered an open-source license due to the non-commercial restriction. If this is meant to be internally consistent, update either the open-source answer or the license selection to match the intended classification.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 1 introduces a bullet list but currently ends abruptly at “GitHub”, making the list read grammatically incomplete. Consider ending line 1 with a colon (or otherwise completing the sentence) so lines 2–3 are clearly introduced.