RexSystem1 voteoriginally by @frenzeldk on GitHub1 reply
I can only support this. It creates transparency while still allowing for a smooth reading experience. Both Facebook (I know, I know) and Discourse support this feature. Not supporting it allows for some nasty surprises, where Mallory writes a message, Bob replies, and Mallory changes their message to make Bobs reply look bad.
One addition could be to allow edits with the first 5 minutes (time frame subject to discussion) where the edit is only visible to instance staff, community owners and/or moderators.
RexSystem1 voteoriginally by @Tagette on GitHub OP
Can always delete the post to hide the secret while you rush to change it but I see your point. Someone might not realize people can see the history and the password is still being shown. Perhaps instead the new history entry is hidden for a delay before it is revealed in the list.
I think the best solution would be to have a dedicated "I leaked a secret" button or something like that. So when it happens Fluxer can hide the history for a set amount of time so they have a chance to change their password or w/e. Moderators can override this with an audit entry in case they need to resolve some situation in a hurry. Though, that's a lot more than this task was supposed to be.
Honestly, people will get used to it over time and learn to delete their message instead of editting it to hide a secret. Or even better, stop sharing passwords over chat...
P.S. There have been times where I have editted a message for good reasons many days or months later.
Thread
Comment by @frenzeldk
Comment by @Tagette