Yeah, that was my point in the first comment… But not only that…
The development with multiple people is decentralized, yes…
But even, if I add 3 remotes to my repo (1 to GitHub, 1 to Forgejo instance A and 1 to Forgejo instance B), guess what happens, if you don’t have an account on each of these… Try pushing code or making a pull request and see how it fails, because you are not authenticated…
SourceHut encourages an e-mail–based workflow that does not require anyone but the repository owner to have an account. In fact, that’s how Git originally worked before GitHub enshittified it.
Git is already decentralized, nothing is stopping you from adding multiple remotes to your repo.
The issue tracker is usually the concern
Yeah, that was my point in the first comment… But not only that…
The development with multiple people is decentralized, yes…
But even, if I add 3 remotes to my repo (1 to GitHub, 1 to Forgejo instance A and 1 to Forgejo instance B), guess what happens, if you don’t have an account on each of these… Try pushing code or making a pull request and see how it fails, because you are not authenticated…
SourceHut encourages an e-mail–based workflow that does not require anyone but the repository owner to have an account. In fact, that’s how Git originally worked before GitHub enshittified it.
How would decentralization work for an issue tracker? The issues have to be stored somewhere.
naturally on the instance that hosts the repo
The issues should be central, but it would be nice for my reputation as a contributor to migrate between instances.