2 ms·
Not "empty" in the literal sense, but no information (e.g "EDIT: nm")
by minimaxir 11y ago
Not "empty" in the literal sense, but no information (e.g "EDIT: nm")
- krapp 11y agoFair enough - I guess that is technically valid. I don't know whether disallowing edits after a post has replies as well would be the easiest way to fix that - you would have to handle the edge case where a comment gets its first reply before an edit is made. Maybe have comments start out as drafts, and only allow edits before they're published? An edit log might work too but what do you do when an edit changes the entire context of the thread that follows it? If you allow edits in a comment with replies, you could treat each edit and its current comments as a separate unit, so that each edit results in a new thread (a bit like separate branches in a git repo) but that would probably be a serious pain to navigate.
- dang 11y agoIt's important to let people save face when they say something they regret. We're moving the window a little toward accountability here (the fact that an account said something that got a reply is now immutable), but only a little. Public edit logs would be going much too far, I think.