Oddbean

Edits are bad because they break NIP-01, they leads to inconsistencies, they lead to more complexity (and less efficiency) and a few other reasons. nostr:nevent1qvzqqqqqqypzprhy9yxf3vst9xv38zej9arxagsvw4sg7452k570z9yjh7djapyuqy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcqyqu72u49vh94kfq6elfp50sq4prnxng42qxe7q3lhy7r89vhy65cx273rt5

My user experience with unmodifiable and undeletable notes makes nostr close to unusable. When I post a note with mistakes that make it illegible, i'm faced with either replying to my own note with corrections, or posting a new note. This makes the recipient's experience degraded, and forces both parties into an idealology they have no connection to. The object to nostr isnt to make it some kind of pure programer's panacea, but to enable uncensorable communication while balancing ease of implementation to encourage adoption with enabling expansion of scope within the new communication protocol's M:N paradigm. Regarding lack of consistency of relays and potential forking of versions, this is something that exisis already with any replaceable events such as the profile information, but for notes it can easily be resolved on the client side by comparing revision data.

> When I post a note with mistakes that make it illegible, i'm faced with either replying to my own note with corrections, or posting a new note. Replying to your own note is the right path. > This makes the recipient's experience degraded, and forces both parties into an idealology they have no connection to. What's the ideology in question? @Laeserin did make some ideological points against edits, but none of the points I made are ideological. In fact, they are mostly technical concerns. > this is something that exisis already with any replaceable events such as the profile information Yes, this is true and it's possible to see different info for the same account depending on what relays one uses. Therefore, one shouldn't trust account info to be consistent. Accounts info are metadata. One doesn't generally reply to an account description or reference it. Consistency is less of a concern, but modifications are arguably more important because it doesn't simply represent a statement made at some point in time. Also, one doesn't generally identify (and verify) account info by an hash, but, rather, by the user ID, so account info wouldn't be necessarily consistent even if modifications were not allowed. > but for notes it can easily be resolved on the client side by comparing revision data. That means having to pull more data from relays, instead of stopping at the first answer which one can verify given the ID.