I like this one.
I thought this was an elegant solution, but it's sort of just stalled.
https://github.com/nostr-protocol/nips/pull/1076#issuecomment-1987002929
Discussion
I's still a fan of using kind+1 for replies but I think I'm in the minority. Still NIP-22 is a better solution than kind 1s
anything to stop using kind 1 😀
Kind 1 with a k Tag or a generic comment kind are both "final implementations" (you rebuild it once and you're done). Seems neater than plan Kind 1s, at least.
even kind 1 with a "k" tag wouldn't fix the issue of social clients having to filter out every reply just to show a timeline
a generic comment kind would be a clean solution since it would not show up in the social timeline and would allow clients to show just the replies
however NIP-22 might need to include "p" tags for notifications
I'd argue a generic comment kind would be well-served by AsciiDoc support, as it opens up more rich text options and makes the kind 1111 events appealing in a broader range of use cases.