The problem is communities congregate where they are the largest. You can move yourself off of lemmy.world, but you can’t move your community off of lemmy.world. You could make communities less dependent on the host they are on or any given moderator group, but Lemmy’s design is not that. So you can sever yourself off of it, and now you are left the option of joining far smaller and less active alternative communities.

I don’t believe it would be that hard to make a lemmy style federation where if your host or their moderator groups ban you, other hosts could still see you. That used to be the case with kbin, people could comment in communities based on instances that had banned them, even if those comments would only be seen in kbin. It was easily exploitable, because it bypassed moderation controls for the home instance and would really have required moderation group for that instance, but it could be done.

Imagine having links to communities like, https://lemm.ee/c/[email protected] ,but being capable of specifying a different moderator group / messaging handler dispatcher (or whatever the component in charge within an instance of determining which comments to inform users of is called) from another instance like, https://lemm.ee/c/[email protected]:lemm.ee , that would just default to the official if there wasn’t any instance local group in charge. But that would cause so much drama because these positions attract control freaks.