mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-22 16:35:52 -05:00
Update 112.md
use "r" tag to match other nips
This commit is contained in:
parent
95173c44d3
commit
e84206b60c
6
112.md
6
112.md
|
@ -51,7 +51,7 @@ A list of recommended relays SHOULD be added to the channel-create message
|
|||
```json
|
||||
{
|
||||
"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 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
|
||||
{
|
||||
|
|
Loading…
Reference in New Issue
Block a user