[Bug]: Contents of removed comments are no longer visible via API for moderators and admins about lemmy HOT 5 OPEN

Creators should be able to see contents regardless of whether content was removed or deleted.

Torn about this one, mainly because of the extra complication required in UIs just to view this data, when you can already easily click restore / undelete, and it'd be much faster.

For the other two concerns: We've added an API request / dropdown for posts and comments, where you can see the moderation history of an item. So admins / mods can view removed content there, and see the entire history of it too.

from lemmy.

Creators can't restore removed comments, only deleted ones.

Restoring deleted comments may expose content that they intended to keep removed for everyone, even if just temporarily.

For moderation history, that is still lacking imo. Based on what's available in lemmy-ui, it seems that this is just a modlog excerpt, but modlog is not populated with every individual post/comment that was removed as a result of banning a user with content removal.
Arguably, this could also be considered as a feature request for modlog to include all those entries as well, which with per-post/comment modlog view is probably even more important now.

I haven't looked at the API yet, wouldn't this require a modlog API call for each individual comment?
Let's say I am an instance admin looking through a users profile. This profile shows 20 comments, which are all removed, and I want to review if these comments are just something the community mods don't want in their community or the user should be banned entirely, e.g. for harassment or trolling.
Now for a client to display me this content, 20 additional requests would have to be made to get modlog for all these comments, just to obtain the original content.
Granted, an admin or client could just look at the target users modlog instead of per item modlogs to make their decision, but then they might have to go through a bunch of pages of modlog, which may or may not have duplicate events concerning the same item, content displayed out of creation order and isn't unlikely to require pagination to ensure getting all relevant modlog entries.

Dealing with recent trolls, often content is removed by community mods prior to admins being made aware, so it is crucial to have easy access to this overview to prevent them from expanding to other communities.

from lemmy.

modlog is not populated with every individual post/comment that was removed as a result of banning a user with content removal.

Could you create an issue for that? I agree each comment / post removed should have a modlog entry.

Let's say I am an instance admin looking through a users profile. This profile shows 20 comments, which are all removed, and I want to review if these comments are just something the community mods don't want in their community or the user should be banned entirely, e.g. for harassment or trolling.

The modlog already supports filtering by user, eg https://lemmy.ml/modlog?page=1&userId=7904

So we'd just need to add either a dropdown for lemmy-ui to navigate there, either from the post / comment dropdowns, or their profile page.

Restoring deleted comments may expose content that they intended to keep removed for everyone, even if just temporarily.

This would still need a clean UI flow, for: you deleted your comment but want to see it again, but don't want to restore it. The temporarily making it public / private to me seems pretty minor, since it was public before you deleted it anyway.

from lemmy.

Could you create an issue for that

Done: #4699

The modlog already supports filtering by user

This is only part of the answer though. Frequently I want to see not only present or only removed comments, but the timeline of comments created on a user's profile.
In a comment thread, I frequently want to see context for other comments, e.g. to determine whether an inflammatory comment was intentionally baited.

The screenshots below are not vanilla lemmy-ui, but they demonstrate the client capabilities.
I'm currently using this with a hacky userscript.

from lemmy.

0.19.3 was essentially bugged behavior... and it leaked not only removed, but deleted content also. I'm still torn on whether to include this special case for admins only, or just rely on the existing modlog.

but the timeline of comments created on a user's profile.

That is exactly what the modlog filtered by user shows.

I'd need other devs to chime in on this one.

from lemmy.