From 4beca330efcff0efb43a04c7f78c3020b382a939 Mon Sep 17 00:00:00 2001
From: Oscar Merry <oscardmerry@gmail.com>
Date: Mon, 11 Nov 2024 15:10:59 +0000
Subject: [PATCH] Live Events - Optional Pinned Chat Messages

---
 53.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/53.md b/53.md
index c3f15ea0..cd84e4fe 100644
--- a/53.md
+++ b/53.md
@@ -35,7 +35,8 @@ For example:
     ["p", "91cf9..4e5ca", "wss://provider1.com/", "Host", "<proof>"],
     ["p", "14aeb..8dad4", "wss://provider2.com/nostr", "Speaker"],
     ["p", "612ae..e610f", "ws://provider3.com/ws", "Participant"],
-    ["relays", "wss://one.com", "wss://two.com", /*...*/]
+    ["relays", "wss://one.com", "wss://two.com", /*...*/],
+    ["pinned", "<event id of pinned live chat message>"],
   ],
   "content": "",
   // other fields...
@@ -75,6 +76,8 @@ Event `kind:1311` is live chat's channel message. Clients MUST include the `a` t
 }
 ```
 
+Hosts may choose to pin one or more live chat messages by updating the `pinned` tags in the live event kind `30311`.
+
 ## Use Cases
 
 Common use cases include meeting rooms/workshops, watch-together activities, or event spaces, such as [zap.stream](https://zap.stream).