I agree with you about user choice. I guess where I get stuck is the “replace the original post” part. There’s something about it that feels disingenuous, or maybe just less “raw”.
If my client showed an “edited” note, with an indicator that it’s been edited, along with a way to view previously signed versions, that wouldn’t bother me the same way.
As I’m thinking through this, it’s not that I have a problem with simply revising or improving content, but more with giving users the idea (similar to “delete”) that something they signed and published can ever actually be removed. That’s the part that feels problematic, the false sense of security it may give a user.
This is true of the internet and digital information as a whole, of course. But that’s what is so refreshing about “no edits” on Nostr — the honesty about information (and especially signed content).
It sounds like what I wrote about “new versions” is actually how the edit feature would work. So in that case, it comes down to the client, and whether it honors the fact that previous versions were signed, if it hides/obscures past versions without letting the user know.
> If my client showed an “edited” note, with an indicator that it’s been edited, along with a way to view previously signed versions, that wouldn’t bother me the same way.
That's exactly what Amethyst does. Full edit history is available and the edited post is marked as such. Which is way better than the standard replaceable events used in nostr's blog clients for instance.
Well, that’s awesome. Never realized this! Is it an amethyst-specific spec or just a NIP that other clients ignore? How would one of these edited posts appear in another client — multiple similar notes from the same npub?
Now I’m starting to wonder if some of the “accidental double posts” I see are actually edits where I didn’t notice minor revisions 🤔
You’re making me rethink my position, Vitor. Dammit. (Although I still think I wouldn’t edit my OP even if I could 😉)
It's a NIP proposal right now https://github.com/nostr-protocol/nips/pull/1090
I’ll be very curious to see how it plays out across different clients. Thanks for taking the time to discuss it here; this was exactly the sort of counterargument I was hoping for, to flesh out gaps in my own knowledge.
Now I’m curious, as a Damus/iPhone user, what our friend @jb55 thinks about this prospect. I recall us agreeing that no edits are better, a year or so ago, but (as with anything) there’s nuance and I get to expand my perspective by simply hanging out with you guys here.
Will, is this something one might see implemented in Damus, if the NIP is merged? Would users have the choice to disable/ignore it? Makes me wonder whether the UX of ignoring edits would actually be worse, despite being more “honest”.
I guess it’s back to the asterisk of pointing to previous versions, rather than “pretending” a note had been that way all along. That satisfies my objection to the misleading nature of edit/delete on the internet.
I do still like the concept of “once it’s sent, it’s sent” and how that could subtly shift behavior toward more thoughtfully written notes. But that’s not for me to push on others 🤷♂️
I like the delete and redraft edit spec by fiatjaf. No issues with determining what version a user is replying to. You retain "whats done is done" semantics.
Interesting, I’m not as familiar with this one. If it deletes… doesn’t that “hide” the initial post (and thus give the illusion of a delete)?
Did a quick search but couldn’t find fiatjaf’s NIP, but someone on Reddit recommended delete.nostr.com if that’s related?