Discussion Type

General

Discussion Content

Hello GitHub Support,

My account @w0fbyte was suspended today (May 11, 2026) while I was
pushing a new release of my repository w0fbyte/tele-cloud. I would
like to appeal this suspension and provide evidence that the
repository complies with the upstream project's license.

CONTEXT

w0fbyte/tele-cloud is a community build based on the public,
fork-enabled project dabeecao/telecloud-go
(https://github.com/dabeecao/telecloud-go). The upstream repository
is licensed under GPL-3.0 and its allow_forking flag is true
(visible via the GitHub REST API).

I did not use the "Fork" button; I cloned the source and started my
own repository because I wanted to make substantial modifications
that would not be appropriate as a pull request. GPL-3.0 explicitly
permits this, provided the derivative work (1) stays under the same
license, (2) preserves copyright notices, (3) marks prominent changes,
and (4) makes source code available — which it does.

EVIDENCE OF COMPLIANCE

1. The LICENSE file in my repository is the unmodified GPL-3.0 text
   from the upstream project.

2. The top of main.go contains an explicit attribution:

   // Community modifications (C) 2026 @w0fbyte
   // This file is part of the TeleCloud community build by @w0fbyte,
   // based on the original work (C) @dabeecao —
   // https://github.com/dabeecao/telecloud-go
   // Distributed under the same license as the upstream project
   // (GPL-3.0).
   

3. Both readme.md (Vietnamese) and readme_en.md (English) include a
   prominent "community build" banner at the top linking back to the
   upstream repository, and a dedicated acknowledgements section:

   Special thanks to @dabeecao, the original owner of
   dabeecao/telecloud-go, for creating TeleCloud.
   

4. The application's startup banner and /healthz output show the
   string "TeleCloud … - Community build by @w0fbyte", so end users
   running the binary are also told this is a community build.

5. Source code is public, so the GPL-3.0 § 6 distribution requirement
   is satisfied.

6. The upstream repository is still publicly accessible at
   https://github.com/dabeecao/telecloud-go, and its GitHub API metadata
   (https://api.github.com/repos/dabeecao/telecloud-go) shows:

   • "license": { "spdx_id": "GPL-3.0" }
   • "allow_forking": true
   • visibility: public

POSSIBLE CAUSE OF AUTOMATED FLAG

Because I started a fresh repository instead of using GitHub's Fork
button, your automated systems may have treated the code as an
unattributed re-upload. In reality every copy of the code and every
copy of the binary I distribute names @dabeecao as the original author
and links back to the upstream repository. If @dabeecao submitted a
DMCA complaint, I am happy to cooperate directly with them or to
rework the attribution further.

WHAT I AM ASKING

Please review the repository and, if the flag was automated, restore
the account. If @dabeecao filed a takedown request, I would appreciate
being given the chance to address their specific concerns before the
repository is removed permanently.

If more information would help, I can provide:

• A full copy of the LICENSE, README and INTRO files
• A diff between my repository and the upstream, showing the scope
  of the modifications
• The commit log showing progressive community changes over time

Thank you for your time.

Best regards,
@w0fbyte