I argued for multiple relay hints a long long time ago but it didn't get any traction, got pushback on being too much overhead instead, and pushback on the fact that these things rot over time.
The NIP-02 relay hints are 3rd party. Somebody's follow list claims somebody else uses that relay, but do they really? That is why I don't use them for authorative data.
The authorative data is NIP-65 kind 10002 (and new 10050 for DMs). That is meant to be the real deal.
But in case somebody didn't publish what relays they use, there are fallbacks:
1) The contents of kind-3 (although not documented in NIP-02), since some clients put them in there for self-configuration
2) relay hints in other people's kind-3 (NIP-02), but these are 3rd party
3) NIP-05 nostr.json may have relays, but nostr.json is unsigned!
4) Maybe you saw their events on a relay before, so you might remember that as a possibility
5) Any 'p' tag can have a relay hint (again 3rd party, plus they rot, but if you have nothing else....)
Gossip keeps all these relationships and scores them, and it has been a long road of tweaks to that system to get where it is today. If all the other clients did the outbox model, I could throw all that stuff away and just use NIP-65 and be done.
M. Dilger /
npub1ac…9p35c
2024-08-29 21:26:38
in reply to nevent1q…njw4
Author Public Key
npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35cSeen on
wss://relay.noswhere.comPublished at
2024-08-29 21:26:38Event JSON
{
"id": "a4d6a415d17a8585d2a2e4ba27114bb3d32e66c8b193c90a7cf5a1b2333723d2",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1724966798,
"kind": 1,
"tags": [
[
"p",
"dd2057556f88a64cacd075d007f1be480f949c91fd6d0c4d593baccdb2aabde2"
],
[
"e",
"000060fd71eef355cf92cc70722baf7042b5c27482cb78339fe7b563bb9e871c",
"wss://nos.lol/",
"root"
],
[
"e",
"2ce5dc06cdb53c5cca62381c54a5aaa152e7a81236601ccf691f45b5d41959a8",
"wss://nos.lol/",
"reply"
]
],
"content": "I argued for multiple relay hints a long long time ago but it didn't get any traction, got pushback on being too much overhead instead, and pushback on the fact that these things rot over time.\n\nThe NIP-02 relay hints are 3rd party. Somebody's follow list claims somebody else uses that relay, but do they really? That is why I don't use them for authorative data.\n\nThe authorative data is NIP-65 kind 10002 (and new 10050 for DMs). That is meant to be the real deal.\n\nBut in case somebody didn't publish what relays they use, there are fallbacks:\n1) The contents of kind-3 (although not documented in NIP-02), since some clients put them in there for self-configuration\n2) relay hints in other people's kind-3 (NIP-02), but these are 3rd party\n3) NIP-05 nostr.json may have relays, but nostr.json is unsigned!\n4) Maybe you saw their events on a relay before, so you might remember that as a possibility\n5) Any 'p' tag can have a relay hint (again 3rd party, plus they rot, but if you have nothing else....)\n\nGossip keeps all these relationships and scores them, and it has been a long road of tweaks to that system to get where it is today. If all the other clients did the outbox model, I could throw all that stuff away and just use NIP-65 and be done.",
"sig": "2dd66c0b842ce67b4e219f65b023511a69acf9fbd7946096f2cdadd65c67207e0724e966db59a23e78d2396af82e24b31115241551e0c4b633319b5f5b82f694"
}