From a6f7f4b4cc3dba8e8092324da59da8df66c1437c Mon Sep 17 00:00:00 2001 From: Fmar Date: Sat, 14 Oct 2023 23:29:24 +0200 Subject: [PATCH] add prioritization (by trust) of list guidelines --- 65.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/65.md b/65.md index b676029..656d145 100644 --- a/65.md +++ b/65.md @@ -61,3 +61,7 @@ This NIP allows Clients to connect directly with the most up-to-date relay set f 5. If a relay signals support for this NIP in their [NIP-11](11.md) document that means they're willing to accept kind 10002 events from a broad range of users, not only their paying customers or whitelisted group. 6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-6). + +7. Clients SHOULD guide users to treat the list as prioritized, with most trusted relays (less probability of censoring events, like a personal relay) at the top. + +8. When seeking events **from** a user, clients SHOULD if possible start by using the relays most at the top of list, since these should be the most trusted by the user.