A very long text that comes two years after the proposal explaining how allowlist-based networks could work, why they are needed and all:
https://writer.oliphant.social/oliphant/islands
In short, it’s not just about each instance having its own allowlist, it’s about multiple instances in allowlist-mode creating a network with each other, all of them bidirectionally federating, based on commonly agreed rules. It’s a way to favor a nice experience by default rather than the neverending task of getting harassed, moderating, etc…
Tools needed to be built. Shared reporting and actions, endorsements, dynamic additions/removal, shared spaces for communicating… This link explains it all and is an invitation for everyone to consider building such networks, small and large, closed or open
There are levels to this. For sure, if we could automatically block instances with open signups and no manual verification, the worst of the worst would be eliminated and we could start with that. In fact I believe the author has a project of creating a larger-scale network of instances more or less like that, called Pangea.
The nice thing is that however strict you want to be, there’s a chance the same tools will be needed anyway, up to you to configure, and this is what Pelago does. No matter what you do with it, it becomes more useful to everyone and I like that. Doing what you’re proposing helps those with stricter rules and vice versa !