[everybodyknows]

The escape path is to demote Github to merely an "officially supported mirror" of your project, with Issues and PRs elsewhere, but ...

The tar-pit I'm afraid of: How do you emigrate Github PR and Issue databases in some format that any of self-hosted Forgejo, or public Codeberg, Gitlab et al understand and can present to visitors?

[dpkirchner]

I understand why companies do this but I sure don't like it. They often use Discourse, which I find to be a lot less readable than GitHub (the design follows what I call "duploification" -- the elements are all large and surrounded by too much whitespace!)

On top of that it's yet another site I have to sign up with if I want to interact with the community.

I'm also mindful of the risks of centralization. Discord and its lack of external archives is a prime example of how that can be harmful. I'm just not sure if that risk outweighs the costs and annoyances.