nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

make the usage of punctuations uniform

Browse Source
This commit is contained in:
jiftechnify 2023-10-25 12:27:18 +09:00 committed by fiatjaf_
parent 749c9b0a2d
commit 6b566e897c
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
65.md
View File

@ -23,26 +23,27 @@ The `.content` is not used.
], ],
"content": "", "content": "",
...other fields ...other fields
}
``` ```
This 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. This 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.
## When to Use Read and Write Relays ## When to Use Read and Write Relays
When seeking events **from** a user, Clients SHOULD use the WRITE relays of the user's `kind:10002` When seeking events **from** a user, Clients SHOULD use the WRITE relays of the user's `kind:10002`.
When seeking events **about** a user, where the user was tagged, Clients SHOULD use the READ relays of the user's `kind:10002` When seeking events **about** a user, where the user was tagged, Clients SHOULD use the READ relays of the user's `kind:10002`.
When broadcasting an event, Clients SHOULD: When broadcasting an event, Clients SHOULD:
- Broadcast the event to the WRITE relays of the author - Broadcast the event to the WRITE relays of the author
- Broadcast the event all READ relays of each tagged user. - Broadcast the event all READ relays of each tagged user
## Motivation ## Motivation
The old model of using a fixed relay list per user centralizes in large relay operators: The old model of using a fixed relay list per user centralizes in large relay operators:
- Most users submit their posts to the same highly popular relays, aiming to achieve greater visibility among a broader audience. - Most users submit their posts to the same highly popular relays, aiming to achieve greater visibility among a broader audience
- Many users are pulling events from a large number of relays in order to get more data at the expense of duplication - Many users are pulling events from a large number of relays in order to get more data at the expense of duplication
- Events are being copied between relays, oftentimes to many different relays - Events are being copied between relays, oftentimes to many different relays