I think it's mostly a UX problem. On the write side, allow a chain of self-replies. On the read side, identify self replies that happen at the same time as the parent and show those as a thread. 7D isn't the right solution, and requires completely different UI, since it doesn't allow for replies to replies.
Replies (4)
I want to avoid having all these as different things to render:
- Kind 1 Note
- Kind 11 Post without subject
- Kind 11 Post with subject
- Kind 30040 type: thread (since that would be the only clear Thread spec then)
I don't see the need to reinvent Kind 1 with NIP-7D.
We can just start replying with Kind 1111s on Kind 1 and have the same thing. Especially if no one is using the subject anyway.
If you solve for Threads client-side, than the current Kind 1 is already good enough.
> I don't see the need to reinvent Kind 1 with NIP-7D.
We're not, it's a completely different concept. It's intended for use in old-school forum-like apps, not in kind 1 apps.
That's what I'm saying
