Thanks. From the linked discussion, it does solve a legitimate problem - I had noticed that entire comment branches could be lost if a parent comment was deleted or removed. That was also pretty bad, so I’m glad there’s been progress there.

Honestly I think reddit’s approach is correct: when I delete my comment, other see that a comment existed here once, but not what it said or who wrote it, and it’s no longer interactive. And, deleting it doesn’t affect child comments.

Fair, I was hoping it’d be something you could configure. Hopefully this improves with Lemmy in the future then.

maybe to you ¯\_(ツ)_/¯

Everything you post online can and will be instantly archived by data hoarders and data corporations

I don’t agree with your implication that because someone somewhere might be archiving my comment, then there’s no point in giving users a proper delete button.

There’s also a huge difference between my comment being publicly accessible in the original thread versus stored elsewhere in some archivist’s database. Obviously nobody can control the latter but that doesn’t mean there’s no point in controlling the former.

I know that. But at least that’s not really publicly listed for anyone to load from my home server in the original comment thread. And that’s beyond the server host’s control anyway; it’s completely within the server host’s control to decide to delete something properly on request or not, so choosing to not delete it is just weird.

Rather than having some control over my comment in the source thread on the source server, I now have zero control at all. That’s not a good user experience.