From 33e9e439483823dd1b94f3c6a78268479926471c Mon Sep 17 00:00:00 2001 From: kehiy Date: Thu, 12 Sep 2024 16:29:12 +0330 Subject: [PATCH] nip-29: restriction for _id_ --- 29.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/29.md b/29.md index 6232f8b..43817a1 100644 --- a/29.md +++ b/29.md @@ -8,7 +8,11 @@ Relay-based Groups This NIP defines a standard for groups that are only writable by a closed set of users. They can be public for reading by external users or not. -Groups are identified by a random string of any length that serves as an _id_. +Groups are identified by a random string of any length that serves as an _id_, generated by client. + +_id_: is restricted to the characters `a-z0-9-_.`, case-insensitive. + +the relays MUST decide to reject creation of a group if an _id_ issued by client is not following the above restriction or MAY reject the creation if it's already exist or that's not acceptable based on their policies. (e.g. length of _id_ is too long). There is no way to create a group, what happens is just that relays (most likely when asked by users) will create rules around some specific ids so these ids can serve as an actual group, henceforth messages sent to that group will be subject to these rules.