disclaimer: i maintain tangled, some reasons to try might be:

- tangled federates: https://blog.tangled.org/federation

- native stacked PRs: https://blog.tangled.org/stacking

- tangled implements mitchell's vouch system: https://blog.tangled.org/vouching

It also has a pretty fundamental design flaw: issue /PR comments belong to the server where the commenter is hosted, not to the repo. I’m sure they will find a workaround but finding that reduced confidence they actually understand the problem they are solving.

> something more established like Codeberg, or if f/loss, Forgejo or Gitea?

Codeberg's git hosting is a Forgejo instance, actually.

Yes, separation between git storage and identity. Very simple to use your own Knot instead of the default knot1, just enter your own website link to it. Not as beholden to Github downtimes that are out of your hands.

I was using Codeberg this morning, now I'm on Tangled. All I had to do was switch remote origin.