nip29: support for unmanaged groups, top-level relay-local groups and invite codes #1496
Conversation
| Group identifiers must be strings restricted to the characters `a-z0-9-_`. | ||
|
|
||
| When encountering just the `<host>` without the `'<group-id>`, clients can choose to connect to the group with id `_`, which is a special top-level group dedicated to relay-local discussions. | ||
|
|
There was a problem hiding this comment.
here we can add UUID recommendations and why relays may reject some id.
Also, above we defined the id's. here we defined a way to find a group using id and host, combined. which I believe MUST be replaced with names in future.
There was a problem hiding this comment.
UUID is excessively big and unnecessary, I don't think we should recommend it although some people may want to use it.
There was a problem hiding this comment.
We do not plan to use id's for users at all. also on the other hand for example 0xchat is generating very big id's larger than UUIDs.
There was a problem hiding this comment.
I think that is a bug in 0xchat then, and also relays should block giant ids.
|
NIP 29 needed less complexity, not more! |
|
any updates on this?? |
|
I've written my own counter-proposal on #1495 |
|
got it, will check it. thanks. |
…ermissions" into unspecified "roles".
This basically allows NIP-29 to be used without any moderation in normal relays and the usage of these relays as groups. These can later upgrade to fully moderated relays.
It is a counterproposal to #1495.
This PR subsumes #1493.