Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 52 additions & 0 deletions 2026/06/2026-06-30-jellycolor-v2-hikka.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
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).

---

Hello,

Thank you for your response. Here is my revised, complete DMCA takedown notice including my full contact information (telephone number and address) as requested.

I am the [private] and copyright holder of the code in question.

1. The original copyrighted work:
[private] original repository, published under the MIT License, is located here:
https://github.com/olegcoffiau-source/jellycolor-v2-hikka
The original file is JellyColorV2.py. You can verify by the commit history that [private] initial commit was made on May 18, 2026.

2. The infringing material:
The user justidev-heroku has copied [private] code into their repository but intentionally removed [private] original copyright notice and replaced it with their own name (Copyright (c) 2026 justidev). This directly violates the attribution conditions of the MIT License. By stripping [private] copyright and claiming it as their own, they are infringing on [private] intellectual property.

The infringing file is located here:
https://github.com/justidev-heroku/justi-modules/blob/main/modules/JellyColor.py
As you can see from their commit history, their file was added weeks after [private] original publication.

The infringing file "JellyColor.py" is a direct, plagiarized derivative of [private] original file "JellyColorV2.py". The infringer has deliberately stripped [private] Hikka-specific metadata line "# meta developer: @[private]" (which is [private] [private] [private], recently updated to [private] current active handle @[private]) and replaced it with "# meta developer: @justidev". In the Telegram userbot ecosystem, this metadata line is what displays the developer's handle directly inside the client's interface to thousands of active users.

By replacing [private] developer tag with theirs, and replacing [private] copyright notice with "Copyright (c) 2026 justidev", the infringer is actively misleading the public and committing plagiarism. Under the MIT License, they are strictly required to preserve the original copyright and author attribution. Their intentional removal of [private] developer metadata and copyright notice is a direct violation of the MIT license terms, rendering their use of [private] code completely unauthorized.

3. Contact Information:
Name: [private]
Email: [private]
Telephone: [private]
Address: [private]

4. Required Changes to Bring Into Compliance:
To bring this project into legal compliance with the MIT License, the infringer must apply all of the following changes immediately:
- Restore [private] original copyright notice at the top of the file: "# Copyright (c) 2026 olegcoffiau-source"
- Update the developer handle in the Hikka metadata line to credit [private] active developer account: "# meta developer: @[private]" (formerly @[private], as represented in the original code history).
- Add a clear attribution statement at the very top of the file: "This module is a derivative work based on the original JellyColor module by @[private] (olegcoffiau-source)."

If the infringer fails or refuses to restore [private] current author handle (@[private]) and original copyright notice, the infringing file must be permanently removed from GitHub.

5. Legal Statements:
- 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 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 taken fair use into consideration.
- I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.

Sincerely,
[private]