Update 29.md

This commit is contained in:
K 2024-09-11 21:58:30 +03:30 committed by GitHub
parent 9ecc2b5739
commit a923f55a66
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

6
29.md
View File

@ -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. 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. _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 ## 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. 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](nip-05.md) document to identfy the group with a short humanreadable name, the name can simply point to a group _id_. 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 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 ## The `h` tag