True. But you can do it both ways. You can do relays with peer restrictions or p2p with optional relays. (In which case a relay is just a peer with lots of resources. E.g. a static IP and permissive filters.) You want to have both. I think it makes sense to start with p2p and add relay features, mostly so all the authentication encryption etc just works. It is a bit more of a pain to add it to an existing open relay protocol without leaking metadata. Likewise it is a bigger pain to code for the base protocol of a p2p system because all the data you want is encrypted and routing is a pain. It is just a matter of where you like your pain. I like nostr because you made the practical choice to make it possible to code for. Very bold of you. But I also want to see if I can get there from the other direction. It might actually be simpler in the long run. But I admit getting adoption and making it convenient for developers is.... A long shot at best.