remove "no-text" tag, use "supported_kinds" instead.

1 files changed, 4 insertions, 3 deletions

diff --git a/29.md b/29.md
index ea38f9b..ee74aef 100644
--- a/29.md
+++ b/29.md
@@ -50,7 +50,7 @@ Users with any roles that have any privilege can be considered _admins_ in a bro
 
 ## Live audio/video (AV) spaces
 
-Groups may indicate they support live audio and/or video chat by means of a [LiveKit](https://docs.livekit.io/transport/) server by having the tag `livekit` in the group announcement event. The tag `no-text` should be used if the group doesn't support text, only live AV chat (this is just for informative purposes to the client, the relay should still block events). This setup allows for both Discord-style independent AV rooms and text rooms and Telegram-style single-roomgroup with support for both text and AV.
+Groups may indicate they support live audio and/or video chat by means of a [LiveKit](https://docs.livekit.io/transport/) server by having the tag `livekit` in the group announcement event. An empty `supported_kinds` tag should be used if the group doesn't support text messages, only live AV chat. This setup allows for both Discord-style independent AV rooms and text rooms and Telegram-style single-roomgroup with support for both text and AV.
 
 Upon seeing a `livekit` tag in a group, clients that want to take part in the AV space should call the [token endpoint](https://docs.livekit.io/frontends/build/authentication/endpoint/) at the relay path `/.well-known/nip29/livekit/<group-id>` with a [NIP-98](98.md)-style `Authorization` header to get back the LiveKit JWT and the URL of the LiveKit server and proceed with the stardard LiveKit flow there.
 
@@ -158,7 +158,8 @@ If the group is forked and hosted in multiple relays, there will be multiple ver
     ["picture", "https://pizza.com/pizza.png"],
     ["about", "a group for people who love pizza"],
     ["private"],
-    ["closed"]
+    ["closed"],
+    ["supported_kinds", "9", "11"]
   ]
   // other fields...
 }
@@ -170,7 +171,7 @@ If the group is forked and hosted in multiple relays, there will be multiple ver
 - `hidden` indicates that relays should hide group metadata from non-members. Omitting this tag indicates that anyone can request group metadata events.
 - `closed` indicates that join requests are ignored. Omitting this tag indicates that users can expect join requests to be honored.
 - `livekit` indicates that a group supports LiveKit-powered media rooms (live audio/video).
-- `no-text` indicates that a group doesn't support text messages (can be used to indicate that a group is only usable for live audio/video).
+- `supported_kinds` is a list of stringified kinds numbers the group supports. When not specified all kinds are assumed to be supported. It can contain no items, in which case no kinds are supported (this is the case for AV-only groups, for example).
 
 - *group admins* (`kind:39001`) (optional)