this post was submitted on 09 Apr 2025
6 points (100.0% liked)
Lemmy Support
4836 readers
5 users here now
Support / questions about Lemmy.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I had a look, seems like for the fedimemes post the poster got banned, and probably their post removed:
They likely deleted their account after getting banned
They still posted 6 hours ago: https://lemmy.world/u/cm0002
That image doesn't show "permanently deleted". Neither the comment in the screenshot nor the post the comment was attached to have been deleted. That appears to be a screenshot of a discussion about this issue, rather than an occurrence of it.
Ah indeed, seems to be a different case than the "permanently deleted"
That makes sense, but I'm just wondering if there's any way for an end-user such as myself can easily see this (e.g. modlog, userbanlog, or otherwise) to verify.
From my perspective, I hope you can understand how bewildering it is to have this record gap.
There is no modlog, because there were no mod actions.
There was a mod action: lemmy.ml instance banned that account. It still exists on LW: https://lemmy.world/u/cm0002
I understand, but is there no userbanlog to check as well, where a deleted post is tied to a banned user?
That's what I'm saying. The post is gone because the user deleted their account. Everything about that account is gone. I believe it works that way due to European laws on the right to be forgotten.
Ah I see, so there never will be a userbanlog implemented due to GDPR?
Two separate things.
User bans already appear in the modlogs.
Self deleted accounts don't appear in anything, because they are truly erased.
You know what I'm asking for, can you please meet me mid-way
I am honestly confused.
The existing modlog already includes user bans.
Your comments were never removed, so they don't appear in a modlog.
You can't find the parent posts your comments were made on, because they are permanently deleted due to the poster deleting their account. These don't appear in the modlog, because they were removed by the user, not a mod. There was no reason to attach, because the reason is that the user deleted their account.
If the user had a post deleted by a mod before they then deleted their own account, it won't appear in the modlog, because both the user and the post in question have been removed from the system. If it was in the modlog, all you would be able to see is that an unknown user had some unknown content removed, or than an unknown user was banned, which is less than useful.
If what you're asking about isn't covered by that, then I genuinely don't understand the scenario you're trying to clarify
Aim: Find out why a post is missing
Ideally: Deleted Post -> Deleted User -> Reason for deletion
Reality:
If you see "permanently deleted" in your post history, you know that it was removed because the person deleted their account.
Other than that, there isn't and can't really be any way of tracking that removal, without keeping data that the account owner has requested be deleted. Some clients cache removed content and continue to display it after its removed from the instance, but that only works if the client is explicitly coded to do so, and if the client happened to get a copy of the content before it was removed.
Your comments to their removed post will still show in your history, and the title of the post will be "permanently deleted". If you see that, you know that the user deleted their account. Of note, admins and mods of communities where the content was posted will still be able to view the post stub, to see the other replies to the post, but even they can't see the initial content.
Anything else will have a trail attached to the users ID. The API makes a difference between a user deleting their own post/comment (not account) and a mod doing the same. Many lemmy clients display them differently, though some display them the same, and others just hide as if it never existed in the first place. So in many clients, you can see that a user deleted their own post by the icon the client uses. You won't get any more information than that, because there is no requirement for a reason to be entered when removing your own content.
If a mod or admin removes it, it will show as being removed by mod action, and will generate a mod log.
There is also a purge option that will let a moderator completely purge a user, post or comment from their instance. This is used for accounts that post NSFL content. A purge won't leave a mod log trail, but purging doesn't federate. which means that the content will still be visible on remote instances (and the user can still continue to post if they are based on a remote instance). To remove remote content, the admin needs to issue a ban and content removal before the purge, and the ban will leave a mod log entry. This is only an option if the user was a local user, or for content they posted to a locally hosted community.
In theory, an admin could also remove content directly from the database, but that is basically the same as the purge process. It doesn't federate, so content remains visible on other instances, unless the admin issued a ban before getting in to the database, and then the ban will show in the log.
I guess I don't want to prolong this discussion too much, and I do thank you both for conversing with me so deep to this point.
I hope you can understand a little bit where I'm coming from, where a user such as myself cannot work out whether a post / account was purged due to a user being banned for NSFL content, or because mods are doing something nefarious. Unlike the modlog where decisions are transparent, we just have to take it on good faith that the user was bad.
I thank you for explaining the implementation difficulties in this regard. From the top-level, it does not seem that difficult to me to annotate a dead post with a comment about why a user was deleted (I'm assuming there's a user-deletion log somewhere at the admin instance-level (or even a shared user-ban-list propogated across instances?) this info can be pulled from), but I suppose I can understand how it might be an extra layer of complexity trying to sync such actions.
Feel free to open an issue on the Lemmy Github: https://github.com/LemmyNet/lemmy/issues
This post has been quite interesting to be honest
I sadly don't have a github :'-)
How else can you ensure that a user's data gets deleted when they delete their account?
https://lemmy.ml/post/28337445/17874696
In this very specific case, you would need to check your account profile from another instance (the way I did it, from my instance) to see those posts that would still exist but not on lemmy.ml as they've been banned.