I believe that the addition of an edit history would be a massive boon to the usefulness of Lemmy on the whole. A common problem with forums is the relatively low level of trust that users can have in another’s content. When one has the ability to edit their posts, and comments this invites the possibility of misleading the reader – for example, one can create a comment, then, after gaining likes, and comments, reword the comment to either destroy the usefulness of the thread on the whole, or mislead a future reader. The addition of an edit history would solve this issue.
Lemmy already tracks that a post was edited (I point your attention to the little pencil icon that you see in a posts header in the browser version of the lemmy-ui). What I am describing is the expansion of this feature. The format that I have envisioned is something very similar to what Element does. For example:
What this image is depicting is a visual of what parts of the post were changed at the time that it was edited, and a complete history of every edit made to the post – sort of like a “git diff”.
I would love to hear the feedback of all Lemmings on this idea for a feature – concerns, suggestions, praise, criticisms, or anything else!
This post is the result of the current (2023-10-03T07:37Z) status of this GitHub post. It was closed by a maintainer/dev of the Lemmy repo. I personally don’t think that the issue got enough attention, or input, so I am posting it here in an attempt to open it up to a potentially wider audience.
I didn’t reply after reading the “it’s just text” comment as I didn’t have the time to tackle the long list but I’ll try and add to what you’ve commented as I think you’re at the crux of the issue.
Most solutions to this problem actually store the full version of every text after edit as well as a diff to show what changed. So a 1000 char post with one char modified is 2000 plus whatever the diff is plus the guids plus the timestamps plus whatever else.
Pretty sure that’s what Wikipedia does. They can merge a bunch of older versions together and compress them since there will be loads of repetition. They happily deal with decompression etc since version comparison isn’t widely used by users anyway and they have plenty of money.
There won’t be enough text and versions of Lemmy posts to leverage skip deltas or git-like packfiles.
You won’t want to patch the original post with diffs to produce the latest comment as that’ll just slow everything down.
If Lemmy was enterprise software, sure, have at it with a feature like this but without knowing how often users edit comments, and how many times they edit them, you could end up multiplying your storage costs for no real gain except for a tiny fraction of users who want to see what typo someone corrected.