the thing about relays in URLs is, what relay should the client include? just a random relay from the list? the first? always use the same?
I've tried to use https://minds.com/ as my main nostr client and account, but it failed because no client is watching the minds relay in their hardcoded list of relays (except maybe damus? I didn't try that)
in https://astral.ninja/ people would have to manually input the URL of the minds relay in the settings, other clients (https://alphaama.com/) don't even have settings for that. but it would have been a big hassle anyway.
this is why I think the npub/nshare/nprofile/whatever scheme for adding people along with optional relay URLs scheme is very important.
and that is also why I think clients should start thinking about grabbing relay URLs from event tags so they associate some relays with some users and use that when querying for new notes (i.e. don't try to query notes from a minds user from the wellorder relay and don't try to grab notes from a random user from the minds relay).
how do you see this situation?
Discussion
* relays in tags..
the probability of relays we include in notes today of beeing down in the future is very high, so not sure it really makes sense to do that, it will be mostly bloat in some years time..
Remember all the relays for a user. 1. If you are already listening to a relay in the user's list, use that one. Otherwise just pick one. 2. If the one you picked is down, choose another.
a random relay should be fine. more fancy implementations could count all events from a user they have gotten from each relay and use the one with the most. even fancier would be a count that takes timestamps into accounts (so they can detect if a user has moved between relays).
I don't know, it's probably good to have a little bit of chaos in these things, just don't spread misinformation about relays.