nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 112.md

Browse Source 
use "r" tag to match other nips
This commit is contained in:
earonesty 2023-06-05 03:55:14 -07:00 committed by GitHub
parent 95173c44d3
commit e84206b60c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
112.md
View File

@ -51,7 +51,7 @@ A list of recommended relays SHOULD be added to the channel-create message
```json ```json
{ {
"content": "{\"name\": \"Demo Channel\", \"about\": \"A test channel.\", \"picture\": \"https://placekitten.com/200/200\"}", "content": "{\"name\": \"Demo Channel\", \"about\": \"A test channel.\", \"picture\": \"https://placekitten.com/200/200\"}",
"tags": [["relays", "wss://relay-01", "wss://relay-02", ...]] "tags": [["r", "wss://relay-01"], ["r", "wss://relay-02"], ...]]
} }
``` ```
@ -100,9 +100,9 @@ Clients MAY add additional metadata fields.
Clients MUST specify an "e" tag to identify the channel id. Clients MUST specify an "e" tag to identify the channel id.
Clients SHOULD mark the "e" tag to recommend a relay where the original event can be found. Clients SHOULD mark the "e" tag to recommend a relay where the original event can be found.
Clients MAY replace the "relays" tag with a full list of new relays. Clients MAY replace the "r" tag set with a full list of new relays.
There need be no overlap between the "e" relay and the "relays" list. For example, if a chat channel is moving its relay set to a new set. There need be no overlap between the "e" relay and the "r" list. For example, if a chat channel is moving its relay set to a new set.
```json ```json
{ {