IRC is a good parallel, on large networks you can create, join and get banned from thousands of channels, but you're still on the same network with everybody. You can even get banned from individual IRC servers on the network and still carry on as if nothing happened, because all servers on the network share the same data. Similarly, if one of the IRC servers on the network disappears and never comes back, no channels on the network are affected.
What you are proposing is similar to the hundreds of single-server IRC networks that have the one large channel run by the same people who run the server itself. If you get banned, you've lost access to the channel and all people on that IRC network. You now have to join another one and hope that you can find some of them there. Similarly, if the server gets canned one day, your channel is gone with it.
Your argument is you could run your own IRC server and people could join that. What I'm saying is we shouldn't have to, it's easier and better for Nostr to keep relays generic and solution for communities at a client level, similar in concept to the large IRC networks in this example.
No, my argument is that relays can be like those large irc networks but also run by multiple entities instead of one entity. Large irc networks afaik still have a central entity running the synchronization between the servers.
A large IRC network is a mesh of servers (relays) that all share the same content. They are run by multiple entities because they are multiple individual servers (relays in our example). In this example Nostr is the IRC network, and relays are its servers.
Large IRC network do have central governance, which is usually made up of all individual server operators and used to decide on network-level things, like services, which other servers should be added, etc.
For clarity, I want Nostr to be like those large IRC networks, where all servers (relays) share the same data and all channels (communities) are unaffected by the actions of a single server.
So what I am trying to say (but it's hard) is that you are arguing against community relays and making all kinds of assumptions about how it will work. And now I got suckered into doing the same 😂 I could talk about all the ways nip72 is broken but I won't. I will simply say, it's not clearly defined what community relays or communities are and it's going to take a client or a nip to enter that frontier of unbuilt functionality.
Clients will eventually move away from the blaster model of all notes on all relays. This is already a terrible experience and centralizing force that is killing smaller relays. We already know how to find other npubs via gossip, and we will need a similar way to discover communities otherwise we are all just missing our replies because the messages are on relays that we aren't connected to. And along those same lines, some relays will not want to carry certain topics that is their choice.
The closest thing I've seen to making progress in this realm lately is this nip: https://github.com/nostr-protocol/nips/pull/566#issuecomment-1806961991