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

Add recommended relays set

Browse Source 
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.
This commit is contained in:
earonesty 2023-06-05 03:48:44 -07:00 committed by GitHub
parent fe9ed69dc3
commit 0f6a933079
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
28.md
View File

@ -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
{