Skip to content

NIP-10: kind 1 replies SHOULD be kind 1111 - #2447

Open
alexgleason wants to merge 1 commit into
nostr-protocol:masterfrom
alexgleason:kind1111-replies
Open

alexgleason wants to merge 1 commit into
nostr-protocol:masterfrom
alexgleason:kind1111-replies

Conversation

@alexgleason

Copy link
Copy Markdown
Member

Follow up to #2358

Fixes #523

This is a spooky controversial one that we should all switch to kind 1111 for replies to kind 1, treating kind 1 just like any other kind.

Most modern clients already display it. Now Amethyst, Ditto, and the Mostr Bridge produce only kind 1111 replies.

@derekross

Copy link
Copy Markdown

This makes the most sense to me, treating all replies the same.

@arthurfranca

Copy link
Copy Markdown
Contributor

I support this PR, but not exactly as it's written right now.

I like the idea of using kind:1 events as replies if one wants to publish something similar to a repost, though without creating another branch as a repost would, i.e. keep it as a reply (showing it along with kind:1111 comments) while highlighting it to their follows (showing it on the root events' feed).

Example: I think direct replies to a root kind:1 would be a great fit as a kind:1 event by default, that the user could opt-out from. Opting-out meaning using a kind:1111 event instead.

@arthurfranca

Copy link
Copy Markdown
Contributor

Changed my mind already. I support this PR as-is.

For the idea I mentioned above, just repost the kind:1111 if user wants it to show up on the root events feed. Less complexity.

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.

Filtering events that are not replies (presence & absence filters)

3 participants