Replaceable events is not the right way to handle this use case. Instead, people should be able to issue either annotations that get shown alongside the original note, or patches that modify the note so people can see a history. Ruggability is not a feature.
Discussion
I agree with this !
So you are saying the blog system of 30023 is wrong? Because this one is not any different than that.
Blog content I think is different. It would be nice if it had a history that could be audited, but I think people expect blogs to update their contents more than they expect one-off statements to be modified. One-offs are very granular, they don't have multiple component parts that may need adjustment after the fact. Even so, most blog updates usually take the form of "Update: I was wrong in point 37, @person corrected me."
Not for much longer. Now that Twitter and Threads do provide editable tweets, its only a matter of time to get into everything else.
But yes, ideally we show the history of edits.
So as if you reply to a post with:
Same_npub_says: Wrong**fix.
And the client handles the formatting display as they please on their side?
i agree we should be able to add comments to the note but not modify the original note. you should be able to edit the comment though.
you can look into how wikipedia handles this. they have a very sophisticated system for editing posts i think a lot of people could learn from.
Maybe show that it’s edited and link to the original?
This would work for simple typo fixes. Could even be just kind1s like "s/bitocin/bitcoin". You could issue these manually if your client didn't support a custom UI for editing, and read those manually if your client didn't support magically editing the original post in the UI. Or is this a dumb idea?
Clients would have to self-impose a limit on these though, we can't have giant edits.
Hopefully it remains a niche feature.
I think that would work for typo fixes, prioritized comments (addenda/annotations) would be better for substantial changes.
It’s not “ruggable” if the edit history is there. If you’re saying that a client can choose not to show the edit history, isn’t the same for annotations? (Harder to make a UI around annotations than edit history anyway)
Annotations would be impossible to show as an edit. So either you have the old note, or the old note + context. Editable notes would just get shown unless the client bothers to build an edit history feature, which they probably would not do.
Why would a client show annotations but not edit history? The UI for how to show annotations seems a lot harder to think up and get right. Meanwhile edit history as been done in many non-nostr apps already
Do you think there are places where nostr could significantly benefit from having “diff” kind?
Maybe git or Wikipedia style applications?