From 0f6a9330793e3e53de90cc1c645bc7da811fa5fe Mon Sep 17 00:00:00 2001 From: earonesty Date: Mon, 5 Jun 2023 03:48:44 -0700 Subject: [PATCH] Add recommended relays set The main chat creation message should include a list of relays where the chat is typically found. In addition, when updating the metadata for a chat, the set can be changed (chat has moved) This allows someone to follow a thread of a chat across relays, and it helps preserve censorship resistance properties. --- 28.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/28.md b/28.md index 62ab398f..ef8dc4c8 100644 --- a/28.md +++ b/28.md @@ -24,11 +24,12 @@ Client-centric moderation gives client developers discretion over what types of Create a public chat channel. In the channel creation `content` field, Client SHOULD include basic channel metadata (`name`, `about`, `picture` as specified in kind 41). +In the channel creation `content` field, Client SHOULD include a list of recommended relays for using this chat. ```json { "content": "{\"name\": \"Demo Channel\", \"about\": \"A test channel.\", \"picture\": \"https://placekitten.com/200/200\"}", - ... + "tags": ["relays", "wss://xxx", "wss://yyy", ...] } ``` @@ -49,7 +50,9 @@ Clients SHOULD support basic metadata fields: Clients MAY add additional metadata fields. -Clients SHOULD use [NIP-10](10.md) marked "e" tags to recommend a relay. +Clients SHOULD use [NIP-10](10.md) marked "e" tags to recommend a relay where the original creation can be found. + +Client MAY include a list of new recommended relays, going forward, for using this chat. ```json {