upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjiftechnify <jiftech.stlfy@gmail.com>2023-10-25 12:21:24 +0900
committerfiatjaf_ <fiatjaf@gmail.com>2023-11-06 13:16:42 -0300
commit749c9b0a2d49d09ccbd00f6bdb4843182e334ddf (patch)
tree36eeb351ebef8e851e5ae9bc815a05ce262e8ce3
parent08d3eff350d11657160eca78459da34d9254252b (diff)
clearly define the term "READ/WRITE relay"
-rw-r--r--65.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/65.md b/65.md
index b676029..573e1df 100644
--- a/65.md
+++ b/65.md
@@ -8,7 +8,7 @@ Relay List Metadata
8 8
9Defines a replaceable event using `kind:10002` to advertise preferred relays for discovering a user's content and receiving fresh content from others. 9Defines a replaceable event using `kind:10002` to advertise preferred relays for discovering a user's content and receiving fresh content from others.
10 10
11The event MUST include a list of `r` tags with relay URIs and a `read` or `write` marker. If the marker is omitted, the relay is used for both purposes. 11The event MUST include a list of `r` tags with relay URIs and a `read` or `write` marker. Relays marked as `read` / `write` are called READ / WRITE relays, respectively. If the marker is omitted, the relay is used for both purposes.
12 12
13The `.content` is not used. 13The `.content` is not used.
14 14
@@ -27,7 +27,7 @@ The `.content` is not used.
27 27
28This NIP doesn't fully replace relay lists that are designed to configure a client's usage of relays (such as `kind:3` style relay lists). Clients MAY use other relay lists in situations where a `kind:10002` relay list cannot be found. 28This NIP doesn't fully replace relay lists that are designed to configure a client's usage of relays (such as `kind:3` style relay lists). Clients MAY use other relay lists in situations where a `kind:10002` relay list cannot be found.
29 29
30## When to Use Read and Write 30## When to Use Read and Write Relays
31 31
32When seeking events **from** a user, Clients SHOULD use the WRITE relays of the user's `kind:10002` 32When seeking events **from** a user, Clients SHOULD use the WRITE relays of the user's `kind:10002`
33 33