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

moving kind 0? #1701

Open
kehiy opened this issue Jan 19, 2025 · 7 comments
Open

moving kind 0? #1701

kehiy opened this issue Jan 19, 2025 · 7 comments

Comments

@kehiy
Copy link
Contributor

kehiy commented Jan 19, 2025

based on #1076 i think we can remove kind 0 from nip-0 and move it to a new nip which talks about metadata and profile and keep it there.

@kehiy
Copy link
Contributor Author

kehiy commented Jan 19, 2025

i think we can merge nip-24, 39 and add kind 0 to it. and remove kind 0 from nip 1.

@fiatjaf
Copy link
Member

fiatjaf commented Jan 19, 2025

There is no actual reason to do this. I know that moving things around feels like progress but it's not.

@kehiy
Copy link
Contributor Author

kehiy commented Jan 19, 2025

my reason is to make it clean and make 2 nips united. but i agree with you.

@vitorpamplona
Copy link
Collaborator

I hate NIP-24 so much. It's like a trash can. When we don't have a place to put the thing, it goes there.

@kehiy
Copy link
Contributor Author

kehiy commented Jan 19, 2025

so, why this exist?

@vitorpamplona
Copy link
Collaborator

Mostly because the thinking around the NIP repo keeps evolving. Initially, @fiatjaf didn't need to describe what kind 0 does. It felt obvious. Now we need more and more specifications to make sure things are interoperable.

Since we couldn't put everything on NIP02, nip24 became this weird place to define extra stuff.

@fiatjaf
Copy link
Member

fiatjaf commented Jan 20, 2025

I hate NIP-24 so much. It's like a trash can. When we don't have a place to put the thing, it goes there.

Yes, it's great!

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

No branches or pull requests

3 participants