Looks cool! 🔥
But I was thinking about a different scenario: a client deployed with a hard configuration that locks a list of relays (family, sport-1, sport-2, church, friends-children, friends-parents, ...) that can "auto discover" which relays show to the user testing the access authentication.
I was also speculating if this config can be managed dynamically, for example, using only one hard-coded "bootstrap relay", write accessible by an admin, where he can post kind:10002 events (NIP-65) to populate and update the relays list.
There could be a mechanism (via giftwrapped messages?) to config the accessibility of public relays.
Of course, the two worlds can work hand in hand. I will explore both by design and share the results with you.
