From e84206b60c19459bf6d82e981d608a2b5b33fb11 Mon Sep 17 00:00:00 2001 From: earonesty Date: Mon, 5 Jun 2023 03:55:14 -0700 Subject: [PATCH] Update 112.md use "r" tag to match other nips --- 112.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/112.md b/112.md index a619cf4..d1ada43 100644 --- a/112.md +++ b/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 {