Maybe relay hints should actually be to relay’s pubkeys instead of URLs
Discussion
No, because they are not 1-1 mapped. The pub key of the relay I think is actually the pub key of the owner of the relay.
Yeah, I’m talking about creating a new pubkey per relay not the current admin pubkey they advertise
I paid 15k sats to change my username to my name but it didn’t work - can you please help with that #[1]
How do you discover the relay then?
Don't say "over nostr" because it's not that simple.
If you’re seeing hints you are somehow already connected to some relays so you could query the kind 0 of the relays lr You could use some kind of seeding like what I propose on nostr:npub1pages5yhmncmmfxuza9f9fx68fju0nxnewtlffzrapsufax5mv0sznuw9d ‘ website which is not perfectly decentralized but it’s much more resistant than using domains to find relays
Need to mull over that before I rebute, but I feel like DNS has a good level of resistance to censorship. With so many parts and participants making up the DNS records, for one, you can't just take it all down very easily.
Also there is a quorum at the top of the DNS heirarchy which is somewhat helpful.
I always thought putting mutable address in an immutable event was a bad idea
what about this scenario: each client app has 20 public relay URLs and their md5 checksum, when the owner of new relay wants to add his/her relay to the relay list he/she should send a request to public relay owners, the public relay owners add this new relay URL and relay URL md5 checksum to a table on the relay servers . when a user adds a new relay URL, the client app searches relay URL and its md5 checksum in public relays table and if it was matched the client app adds the relay URL.