Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nip-29: human-readable, url friendly group names. #1484

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

kehiy
Copy link
Contributor

@kehiy kehiy commented Sep 7, 2024

Here is a better, and known way to identify groups for NIP-29 while sharing both group id and host.

Also, the current model: host'id, is not URL friendly.

@fiatjaf
Copy link
Member

fiatjaf commented Sep 7, 2024

If we were to do that it would be better to use it for readable names instead of the canonical group ids, which are meant to be random.

@kehiy
Copy link
Contributor Author

kehiy commented Sep 8, 2024

@fiatjaf Yes, got it. By id, here I mean a readable name of course. Should I add it to the spec?

@kehiy
Copy link
Contributor Author

kehiy commented Sep 11, 2024

@fiatjaf @water783 I've updated the spec. please check. I used NIP-05 this time to point to group id, which is not human-readable and random generated string, but the name itself is human-readable. I've added the detail on how clients can find out how to behave when they see a nip-05 address. but if you think it's not logical we can use another similar thing. this is URL-friendly, easy to share, and human-readable now.

@kehiy kehiy changed the title NIP-29: group IDs nip-29: human-readable, url friendly group names. Sep 11, 2024
@water783
Copy link

Perhaps we can add kind 9009, and authorized admins can request a unique name(human-readable)?

@kehiy
Copy link
Contributor Author

kehiy commented Sep 12, 2024

@water783 you mean admins request human-readable names from relays? it can work as well. and it's a good idea. then we don't need to resolve them like nip-05.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants