You can make a post that says “puppies are awesome”, get lots of people to zap it and reply “agree!”, then update it to “death to all jews” and then there is no way to see the edit history. It just looks like people are supporting that statement with zaps and replies. See the problem ?

Wonder if there are people dare to say they don't see the problem 🤣

Yes, I see it. It's the same problem that exists today with any self hosted blog, of course. Platforms storically solved it disabling or limiting the edit on a short period. Maybe the solution is to include the revisions and make them accessible at comments' level. So if something happens the user can always reply to himself and point out that the comment was related to a different context, highlighting the shady update. A real win would be to somehow force every update/event to include *all* the previous revisions, in this way we can also solve the "vanished from relay" problem, but currently we have only the `d` tag, so revisions are not chainable.

An important and interesting note: what you are worried about is already possible today replacing a image/video linked content, without any formal edit. And it can happens on short notes too. So Damus, like any other clients, is already vulnerable to this sort of "attack".

You are already living the problem with short notes :)

It's a similar issue if I post an immutable kind 1 note saying "I love the https://puppies.com/ website" and then an year later the domain is bought by a nazist group. I think just general education and a caveat in the clients saying that the reply was made to a different event in a different time fixes this as best as possible.

same issue with all centralized links, should we hash something? media should be decentralized anyway, have you seen iroh?

GitHub

GitHub - n0-computer/iroh: IP addresses break, dial keys instead. Modular networking stack in Rust.

IP addresses break, dial keys instead. Modular networking stack in Rust. - n0-computer/iroh

Blergh.

pretty sure this has been thrashed out pretty well in several forum protocols - the events history is not changed, only a new event that says 'edit this event thusly' and then the edited event is displayed with a 'edited' tag on it at minimum, and ideally, a 'view history' button. the event history should be immutable even if a 'change event' event exists.

The "right" way to fix this is to not allow any edits to any post once it has been interacted with in any way - if it's had a like or a zap or a reply. It's the way sensible discussion systems work, and it would make sense to have it do the same here. This is a definite problem, and without any obvious "edited" indicator, it's quite a concern.

no

notes are quite long on amethyst

i will take that as you have no idea what iroh is

Impressive argument you got there

number one there is no proof of time in nostr so you could back date an edit do i need to say more?

exactly

The x tag contains the file hash, you don't need the time attestation to spot a remote update.

note hash, good point but delete already covers this use case edits are good especially as reactions and can be expanded to others doing them, annotations etc, the issues of edits are really a ui problem not the note schema

no