Guessing the pub key serves both the encryption and DNS, basically. Yeah this sounds dumb. There's some obvious ways to both make this private and add some distribution of encrypted data for redundancy. I like nostr's ad-hoc client-relay architecture. I write my events to my own home relay and also forward them to a few public and invite-only relays. But everybody publishes relay lists also so clients can request their content from other relays not on your normal relay list. It's all interoperable and you can customize it however suits you. How is his idea better? 🤣 "Technically more elegant" he claims.