From a923f55a66652b04caa1d247828711479cd4f427 Mon Sep 17 00:00:00 2001 From: K Date: Wed, 11 Sep 2024 21:58:30 +0330 Subject: [PATCH] Update 29.md --- 29.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/29.md b/29.md index 45da98c0..684c2e61 100644 --- a/29.md +++ b/29.md @@ -8,7 +8,7 @@ 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_, generated by client. +Groups are identified by a random string of any length that serves as an _id_, generated by the client. _id_: is restricted to the characters `a-z0-9-_.`, case-insensitive. @@ -22,8 +22,8 @@ Relays are supposed to generate the events that describe group metadata and grou ## Group identifier -The _id_ is a random, not humanreadable string generated by client which may be too long to be shared, or used in URLs. -We can use a [NIP-05](nip-05.md) document to identfy the group with a short humanreadable name, the name can simply point to a group _id_. +The _id_ is a random, not human-readable string generated by the client which may be too long to be shared, or used in URLs. +We can use a [NIP-05](05.md) document to identfy the group with a short humanreadable name, the name can simply point to a group _id_. The domain that serves the NIP-05 related to a group _id_ MUST be the host of the group as well. clients can interpret the address based on where and how they receiver them. ## The `h` tag