Is it normal for an open source creator to be angry you used their code because they "revoked" it?

• inlets

  2 10 10.0 Go

  Expose your local endpoints to the Internet (by the-cc-dev)

  This "" stuff is unneccessary. It took me two minutes to find the repo in question: https://github.com/the-cc-dev/inlets

• inlets-archived

  8 8,407 8.0 Go

  Discontinued Cloud Native Tunnel

  

  This appears to be a very old version of the project before it was eventually forked to a repo that belonged to the inlets org on GitHub. That's why when Alex deleted the github.com/inlets/inlets-archived repo yesterday (a fork he controlled, where all the work since late 2018 was done), this repo under the-cc-dev now appears as the root repo of all the forks that exist right now, including my fork (https://github.com/mattwelke/inlets-archived).

• WorkOS

  workos.com

  sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• inlets-archived

  1 0 1.1 Go

  Discontinued Cloud Native Tunnel, now inlets PRO (by mattwelke)

  This appears to be a very old version of the project before it was eventually forked to a repo that belonged to the inlets org on GitHub. That's why when Alex deleted the github.com/inlets/inlets-archived repo yesterday (a fork he controlled, where all the work since late 2018 was done), this repo under the-cc-dev now appears as the root repo of all the forks that exist right now, including my fork (https://github.com/mattwelke/inlets-archived).

• inlets-archived

  1 0 5.2

  Cloud Native Tunnel (by milindpatel63)

  Here's an example of a fork that is more intact than my fork because the GitHub user forked github.com/inlets/inlets-archived before Alex deleted it yesterday: https://github.com/milindpatel63/inlets-archived

Suggest a related project