1 files changed, 29 insertions, 29 deletions

diff --git a/28.md b/28.md
index 169ae4f..1632088 100644
--- a/28.md
+++ b/28.md
@@ -5,7 +5,7 @@ NIP-28
 Public Chat
 -----------
 
-`draft` `optional` `author:ChristopherDavid` `author:fiatjaf` `author:jb55` `author:Cameri`
+`draft` `optional`
 
 This NIP defines new event kinds for public chat channels, channel messages, and basic client-side moderation.
 
@@ -23,12 +23,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 basic channel metadata (`name`, `about`, `picture` and `relays` as specified in kind 41).
 
 ```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\", \"relays\": [\"wss://nos.lol\", \"wss://nostr.mom\"]}",
+  ...
 }
 ```
 
@@ -37,7 +37,7 @@ In the channel creation `content` field, Client SHOULD include basic channel met
 
 Update a channel's public metadata.
 
-Clients and relays SHOULD handle kind 41 events similar to kind 0 `metadata` events.
+Kind 41 is used to update the metadata without modifying the event id for the channel. Only the most recent kind 41 per `e` tag value MAY be available.
 
 Clients SHOULD ignore kind 41s from pubkeys other than the kind 40 pubkey.
 
@@ -46,6 +46,7 @@ Clients SHOULD support basic metadata fields:
 - `name` - string - Channel name
 - `about` - string - Channel description
 - `picture` - string - URL of channel picture
+- `relays` - array - List of relays to download and broadcast events to
 
 Clients MAY add additional metadata fields.
 
@@ -53,9 +54,9 @@ Clients SHOULD use [NIP-10](10.md) marked "e" tags to recommend a relay.
 
 ```json
 {
-    "content": "{\"name\": \"Updated Demo Channel\", \"about\": \"Updating a test channel.\", \"picture\": \"https://placekitten.com/201/201\"}",
-    "tags": [["e", <channel_create_event_id>, <relay-url>]],
-    ...
+  "content": "{\"name\": \"Updated Demo Channel\", \"about\": \"Updating a test channel.\", \"picture\": \"https://placekitten.com/201/201\", \"relays\": [\"wss://nos.lol\", \"wss://nostr.mom\"]}",
+  "tags": [["e", <channel_create_event_id>, <relay-url>]],
+  ...
 }
 ```
 
@@ -72,9 +73,9 @@ Root message:
 
 ```json
 {
-    "content": <string>,
-    "tags": [["e", <kind_40_event_id>, <relay-url>, "root"]],
-    ...
+  "content": <string>,
+  "tags": [["e", <kind_40_event_id>, <relay-url>, "root"]],
+  ...
 }
 ```
 
@@ -82,14 +83,14 @@ Reply to another message:
 
 ```json
 {
-    "content": <string>,
-    "tags": [
-        ["e", <kind_40_event_id>, <relay-url>, "root"],
-        ["e", <kind_42_event_id>, <relay-url>, "reply"],
-        ["p", <pubkey>, <relay-url>],
-        ...
-    ],
-    ...
+  "content": <string>,
+  "tags": [
+      ["e", <kind_40_event_id>, <relay-url>, "root"],
+      ["e", <kind_42_event_id>, <relay-url>, "reply"],
+      ["p", <pubkey>, <relay-url>],
+      ...
+  ],
+  ...
 }
 ```
 
@@ -108,9 +109,9 @@ Clients MAY hide event 42s for other users other than the user who sent the even
 
 ```json
 {
-    "content": "{\"reason\": \"Dick pic\"}",
-    "tags": [["e", <kind_42_event_id>]],
-    ...
+  "content": "{\"reason\": \"Dick pic\"}",
+  "tags": [["e", <kind_42_event_id>]],
+  ...
 }
 ```
 
@@ -126,18 +127,17 @@ Clients MAY hide event 42s for users other than the user who sent the event 44.
 
 ```json
 {
-    "content": "{\"reason\": \"Posting dick pics\"}",
-    "tags": [["p", <pubkey>]],
-    ...
+  "content": "{\"reason\": \"Posting dick pics\"}",
+  "tags": [["p", <pubkey>]],
+  ...
 }
 ```
 
-## NIP-10 relay recommendations
+## Relay recommendations
 
-For [NIP-10](10.md) relay recommendations, clients generally SHOULD use the relay URL of the original (oldest) kind 40 event.
-
-Clients MAY recommend any relay URL. For example, if a relay hosting the original kind 40 event for a channel goes offline, clients could instead fetch channel data from a backup relay, or a relay that clients trust more than the original relay.
+Clients SHOULD use the relay URLs of the metadata events. 
 
+Clients MAY use any relay URL. For example, if a relay hosting the original kind 40 event for a channel goes offline, clients could instead fetch channel data from a backup relay, or a relay that clients trust more than the original relay.
 
 Motivation
 ----------