Skip to content

NIP-72: prefer kind 11 events for text notes #1932

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

alexgleason
Copy link
Member

NIP-72 uses kind 1 events for text notes, so there is no way to filter them out of regular feeds. NIP-29 groups solved this by using kind 11 which is more appropriate.

@erskingardner
Copy link
Contributor

ack

@staab
Copy link
Member

staab commented May 21, 2025

I think this would just be overloading kind 11 in the same way kind 1 is currently overloaded. nip 72 should have its own kind.

@vitorpamplona
Copy link
Collaborator

vitorpamplona commented May 21, 2025

We could also use NIP-22 events A-scoped to the community itself.

@alexgleason
Copy link
Member Author

alexgleason commented May 21, 2025

I think this would just be overloading kind 11 in the same way kind 1 is currently overloaded. nip 72 should have its own kind.

I thought about that. But nobody queries kind 11 directly. They are always queried with an #h filter (NIP-29) or #a filter (NIP-72).

@alexgleason
Copy link
Member Author

We could also use NIP-22 events A-scoped to the community itself.

I think comments and top-level should still be separate.

@staab
Copy link
Member

staab commented May 21, 2025

But nobody queries kind 11 directly.

Not true, flotilla queries them directly.

@alexgleason
Copy link
Member Author

Not true, flotilla queries them directly.

Why?

@staab
Copy link
Member

staab commented May 21, 2025

Because the relay is the group and I want to show all threads "posted to the group".

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.

4 participants