nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

update to use nip05

Browse Source
This commit is contained in:
kehiy 2024-09-11 21:51:56 +03:30
parent ee48fdf814
commit 9ecc2b5739
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
29.md
View File

@ -8,7 +8,9 @@ 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_. 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.
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. 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.
@ -20,12 +22,9 @@ Relays are supposed to generate the events that describe group metadata and grou
## Group identifier ## Group identifier
To identify a group, we can use NIP-05 like address. for example a group with _id_ of `<id>`, hosted on `<host>` can be The _id_ is a random, not humanreadable string generated by client which may be too long to be shared, or used in URLs.
fined with address of `<id>@<host>`. For clients to don't get confuse with NIP-05 address, they can trait these address 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_.
based on where they are receiving or seeing it. 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.
This makes an easy way to share groups everywhere.
_id_: should be restricted to the characters `a-z0-9-_.`, case-insensitive.
## The `h` tag ## The `h` tag