FWIW, I think deletions on Nostr are a "meh" idea and edits are a bad idea. Consider the following:

- It's an additional layer of complexity. Nostr should arguably be simpler and it's already more complex in some ways centralized platforms are not.

- Different relays will disagree on whether to accept the edit or the delete event, so the original note may stay available. It may also become apparently unavailable and then available again in the future. Someone could send the old version to relays you don't use.

- Unlike some specific features like articles, zaps and whatever one can think of, it only makes sense if consistently implemented, but that's something we can only assume to be true of NIP-01.

- It makes retrieving a note less efficient. You now need to wait a response from all relays, just in case one of them has a deletion or a modification the first one to reply doesn't have.

- There is value in having modifications, but there is also value in having platforms that don't allow modifications, IMO, where an ID truly identifies a specific piece of text and nothing else. Now that Twitter allows modifications, Nostr can use the fact that it doesn't to diversify itself so as to convince users to use both (otherwise the network effect plays against Nostr).

On centralized platforms which allow modifications, users sometimes write a post with the plan of modifying it later. On Nostr that would be a bad pattern, however and I think the modification features can lead to bad usage of Nostr and, therefore, a bad user experience.

Ultimately it will prevail if clients and relays implement it and fail otherwise, but I'm not in favor of it.

the edit could exists as a special selfreply to the original post; if some clients implement it, it seems like an edit (with the visibility of the original), or if some clients don't implement it, it could seem as a normal reply, that corrects the original one

Reply to this note

Please Login to reply.

Discussion

This.

I pretty much mentioned the same thing a while back

nostr:note19kyue5j08wr8vuu6vgf8yhpu0zkwwdth4kwdjtx7c86ulkay4fdswc6e2x

- Show a "show edit history" button and that solves some of the issues.

- Have clients ping a few relays from the user's relay list in the background to see if there's edits. That solves some issues.

- Have edits as a specially reply (there's kind 1 post id, and there'd be its Kind1PostID:0, then :1 , then :2, then :3, etc, and clients present the highest number as the primary post. I'm not a programmer so this prob a dumb way to go about it), that solves some issues.

- A client doesn't have this feature? It shows it as a normal reply. Also, big whoop. People go to clients that does have this feature. The market moves around.

This sounds a like a good compromise solution. Also, I kinda like community notes on Twitter, wish that could be implemented in a similar way.