none yet. but I'm planning on adding support for it in noStrudel for replying to articles and wiki pages, so that will be at least one client
Discussion
This is the challenge. Clients aren't incentivesd to support it because most clients don't publish with it. Clients don't publish with it because most clients don't support it. Catch 22.
A catch 22 is still better than using kind 1 for everything :)
If nothing else then I will try to break the catch 22 with noStrudel
Should we all just use the NIP-22 generic comment thing?
I would love to see a future where we reply to kind 1 notes with NIP-22 replies, then pulling the "default" social feed of kind 1 notes would be so much cleaner
but transitioning to that will take some time and coordination on the part of clients
We need NIP-22 for our books and gitstuff. Don't want everyone replaying with kind 01s, but that's all there is, now.