replies versus kinds #49
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mosaic/nostr-next#49
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replies in nostr are tied up in kinds, meaning there is no orthogonality. You can't be a picture and a reply, a git commit and a reply, or a markdown post and a reply. The "fix" in nostr is to have your reply reference any one of those.
But also there is a difference between being a reply (I want the author to hear this) and being a comment (this is for my followers, I'm not intending to contact the author of the thing I'm commenting on).
I think these all make the most sense being orthogonal from each other, and so they can't all be represented as different kinds.
Replies can be a tag indicating "in reply to" which points to the parent note, and the author of the parent note is also tagged. Any kind could have such a tag.
And comments can be the same, but without tagging the author.