I like edits or at least the theory behind them. I make typos. I want to fix the typos. However, @fiatjaf has convinced me that they're bad. His editing and the gamification of his edits are fun, but if hundreds of people in my feeds are doing this, then it would immediately degrade my experience. I would hate it. It would be annoying.
I now see edits as an attack vector and a performance degrader.
Maybe we need a maximum number of edits? 3? I don't know. I'm just thinking out loud.
Maybe we just do away with them altogether? π
Thoughts?
Thread
Login to reply
Replies (51)
No to edits. Just reply to clarify.
Honestly, why does it matter either way, what other people want, if it's not what you want? Can't people make nostr what they want & you guys not decide for them?
Yes, but developers also need to build something that doesn't hurt Nostr either. It's a balance.


Habla
The case against edits - fiatjaf
Read, Highlight, Write, Bookmark, Earn
Lol I can't tell them what to do. They don't care what I think, and I can't blame them, because I don't think like anyone else.
Fiatjaf can be very persuasive.
On the edit featureβitβs a good example of something users value. People are already paying for it, and it fits well with the idea that users, not centralized entities, should make decisions about their content.
Beyond that, there are so many ways Nostr could grow. Imagine features like markdown support, smart widgets, Taproot finance, global naming, censorship-resistant DNS, Git integration, and personal storage. These kinds of tools could make Nostr even more useful and flexible for developers and everyday users alike.
Nostr was designed to be a place where ideas could evolve quicklyβdifferent from Bitcoin, which thrives on stability. While some folks in the community are cautious about adding new features, itβs worth keeping an open mind. The right updates could make Nostr much more competitive without losing what makes it special.
In the age of LLM generated content I see typos as charming and authentic.
This is a fair point and others have mentioned it too.
ChatGPT are releasing a new model with
more typos. Youll never no. π€£
I rest my case π 

Thinking more like grammar police that correct there, their, theyβre

I'm firmly (and I mean FIRMLY) against the idea of restricting edits or deletion. Sure, taking back something you previously said is alright but if you have a lot of takes in the past that you don't want to keep online, you're going to look really bad.
Plus, it's a major privacy concern. I've made posts in the past that were before I learned the importance of privacy. If I couldn't delete them, I'd be keeping myself open to doxxing, not to mention potential embarrassment. Some posts people make can also damage their reputation. If they made a comment that was written in frustration (or even under the effects of exhaustion or alcohol), their entire reputation could be irreparably damaged if edits and deletion didn't exist. I mean, we see how easily people get canceled for comments they made years ago and forgot about, and society today tends to not accept apologies even when they're legitimate and genuine.
So yeah, no edits/deletion = no use for me. I like Nostr but if a basic function of user control and privacy isn't possible, I will not use it. It's objectively a bad thing and that's a Nostr hill I will die on.
Hard agree. Also we're all about people owning their data. But they can't edit or delete it? Doesn't add up.
Another view point. When you talk face to face to a person or a group of people, once you say something it canβt be edited or deleted. Although a face to face conversation flows at a much faster pace than typing a post online. Not having the ability to delete or edit may make people think more before pressing the send button. You have the time to do so.
I am still open minded about having edits / deletes.
A passing conversation isn't a permanent record, though. Aside from memory, it's not stored ad infinitum. Moreover, if abuse/harassment occurs, such as the canceling thing, it boils down to hearsay.
None of that is even remotely true without edits and deletion.
Transparency for governments, corporations, money and software. Privacy for the people.
Your comment is well thought out. Look at NIP37 that fiatjaf linked to in his comment to my note and see if that allows your usage without compromising the protocol. It seems to. I think it may be the answer for clients to leverage.
I'm in your camp. See any issues with the NIP37 that fiatjaf linked to?
Good points. Thank you. I do think that more thought before posting would be a good idea for many. Absolutely agree, Privacy for the people.
BULLSHIT ON THE DEATH OF EDITS
View quoted note β
how can one be at the same time for covenants and against edit?
require PoW for edits. each edit needs a PoW larger than the previous one. Only the largest PoW will be kept. This will naturally limit edit numbers and reduce spam.
NO EDITS, NO DELETES
I like edits or at least the theory behind them. I make typos. I want to fix the typos. However, @fiatjaf has convinced me that they're bad. His editing and the gamification of his edits are fun, but if hundreds of people in my feeds are doing this, then it would immediately degrade my experience. I would hate it. It would be annoying.
I now see edits as an attack vector and a performance degrader.
Maybe we need a maximum number of edits? 3? I don't know. I'm just thinking out loud.
Maybe we just do away with them altogether? π
Thoughts?
View quoted note →
Oh shhoiure. Juytsc letyy evrynd post udrreaxdble n(;nsensw. That wong cajze proldmz ay all.
Scary thing is, my brain made it easy for me to read that π
Your post needs some serious NIP37.
But "no edit"???
I think that is the edit answer. Allows the edit with chain of changes, or delete replace, depending on how the relay wants to handle it. Backward-compatible, accommodate simple fixes, or in a system that wants to be a mini GitHub for every post they can, use nip 37 to do that on their client relays. This is how I understand it as put forward. Just a matter of getting the clients to onboard it. See my other mock ups for Primal to adopt.
I'd ABSOLUTELY say no edits.
I think it's part of the ethos of Nostr--and a reminder that Nostr is different--it's about privacy, and freedom of speech. No edits are a part of that--
Just like in real life--once you say something, you don't get to pull it back. Yes, you can apologize but your words are forever.
So it is with Nostr.
Think before you speak--both IRL and on Nostr.
No edits is the literal OPPOSITE of privacy and freedom of speech, what are you talking about?
Your argument is also well accepted. I always usually read before multiplying something! Sometimes, it goes unnoticed wrong writings or missing a letter - since I use the cell phone as a transmitter; this gives me a lot of anguish.
Think about it--when you talk to someone you can never "take back" the words you've said....
Same with email...once you've sent it, you can't really pull it back...
If you want to edit your message, do it before you hit send...
#NoEditGang
Edits should just be comments that get prioritized to the top of the feed.
NIP37 would resolve this. Most quick edits of typos won't be substantive and would already be top-of-feed, so you're right in both cases.
I say, Yes to editing on the client layer, because typo. But, I say NO to edits on the protocol layer. There is a greater value to the protocol for the permanance of the notes than to a flexible note for the one user.
Here's my thought process and where I arrived:
I want to know that the post I'm looking at is the post that was placed, and the comments are about this version of it, and the repost are about this version of it. That's important to me as a community observer.
As a contributor, I want to fix my typos.
So, on those times that I look back and see a typo, it's usually right after I post it and before anyone has engaged with it. I just pop over to Nos.social, open the post. Copy the content. Delete the post. Go back to Primal, make sure it deleted, make the post anew with the typo fixed, and resubmit it for all to see without the typo.
That workflow could be provided by Primal. Primal could let me "edit" whereby my original post would be deleted and the new version would be submitted as a new post. After my edit is ready, Primal tells me it's about to request relay deletion of the original post and submit this new version of my post, to which I confirm. That ability could expire after 5 minutes or some short term useful time limit, at the client level.
But, I as the user am not inclined to do that anyway after someone has engaged with it. I'm more likely to just post a comment with the whole "I mean *typo." if it's even worth it. This is the case because the note's consistency after engagement is more valuable to the community than my ability to fix the typo is to me.
This suggested functionality on Primal or any client is my ideal workflow on the protocol, while preserving the important features yet accommodating the necessary one for user experience.
Your replica was interesting to read! It may make sense to be permissive to this, within the protocol.
Finally. A sensible idea.
If NIP37 is already a thing, then it looks like fiatjaf and others have already brought a solve for the clients to leverage. π€
We had this debate years ago on the Steemit blockchain... There's what I believe to be a very simple solution.
Initially, Steemit allowed editing for typos and second thoughts for a brief span (~10 minutes?) after posting.
As an author, I wanted complete control in perpetuity over my work, and fought for that outcome tirelessly.
The final solution?π€
Versioning. Each new edit is saved as a serialized version of the original post. Anyone seeking the "truth" about the ugly, typo-ridden original is welcome to dig back to ground zero, as nothing is deleted, while serious authors can fix typos they may have missed years later.π
Great insight. I like both, but for different purposes. At a protocol level it's oft best to accommodate client desires openly and flexibly and simply. Do you see a fiatjaf describes Nip37 as offering the best of both worlds to the clients/relays on how they choose to handle it, with the end goal keeping a simple flexible protocol? Clients need flex to accommodate infinite use cases. That's the tough job of a protocol.
I hate reading a note, to which I wrote a word wrong or for some reason, I βateβ a letter. So, editing would be valuable - and I wish it was possible to see this tool acting on @primal; my favorite client. I donβt know the size of the impact that this would cause, but for sure, a test in practice could be done; and if it is found that it is bad, excluded later.
Being able to edit the ledger of what has been said is never a good idea.
All I know is I won't be implementing edits in any of my clients Β―\_(γ)_/Β―
An edit mechanism that creates a new note that supersedes the original, while leaving that original intact, would be ideal. We all speak thumb.
@Derek Ross Thinking without edits sharpens clarity and intention. The discipline shapes better ideas upfront.
only buybiby choice ya/bye(^_^)
Edits could be fine... If you can also go and see the original note.
That permanence will add a lot of historic value years down the road even for something as silly as a typo.
The hardness of our words is important to me. We are etching our notes into digital stone.
You can see the edits. All several hundred of them.
Amor π me dijo mi hermano