30
Issue with nsfw material in feed
(lemm.ee)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jul 2023
30 points (78.8% liked)
Asklemmy
43728 readers
1771 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
Ok, I will. The issue is the rule is NOT strictly followed and those posts pop up in my feed regularly.
As far as I can tell mods are swift in dealing with reports. And even though the rule exists there will always be people that ignore those rules. There is no way to block whole instances at the moment and without the NSFW flag, there is no technical way to see that the post contains NSFW image.
In addition to reporting the post in question you could also block the user if you suspect that they are posting without the NSFW flag regularly.
I don't have a link handy, but I saw this reported before and when someone went to lemmynsfw to check the posts, they actually had been properly marked as nsfw.
My unsubstantiated theory is that federation is working pretty crappily right now and so lots of federation messages get dropped. When a new post or comment gets dropped you don't notice because... well... you don't see anything. But when a post makes it through and an edit gets dropped, that can be more visible.
So likely what's happening is that on some small percent but medium absolute number of lemmynsfw posts, someone makes an honest mistake and fails to tag it. They either notice themselves and fix it, or a mod asks them to and they comply... so on lemmynsfw it looks right. But the federation message with the edit gets dropped by your instance, and for you and others viewing from there it forever remains sfw in error, even though all the right steps were taken. I've also heard mods discussing this happening with post removal moderation actions, the post gets removed on the community's home instance, but the federation message containing the removal gets dropped by some big instance and the post blows up there anyway where the mods are actually unable to shut it down.
I don't think there's anything anyone can do about this other than maybe the lemmynsfw admins tuning their federation worker counts (though they may have already and that may no longer be needed in recent Lemmy versions), or the Lemmy devs working on federation scalability so a larger percentages of federation messages get reliably delivered.
I think this is what’s happening. I recently double posted a comment by mistake and immediately deleted the duplicate, but when I came back later in the day, I noticed the deleted comment was still getting upvotes and replies.
Is it possible for an author to change the NSFW tag on a post after the fact? Maybe thats what happened, it's explain the slow federation for the edit.
I can confirm that there are still federation issues. Even purging comments does not always federate to other instances. But this comment explains the situation quite well.
This was the same way this was dealt with in Reddit. Just report it.
I feel like LemmyNSFW should have the NSFW tag by default.
It does in 99% of the communities. Some are not exclusively NSFW content, so it makes sense to make the tag optional in those. It opens the door for novice users to make a mistake though.