Issue with nsfw material in feed
Issue with nsfw material in feed
So this post from lemmynsfw.com just popped up in my feed. It is not tagged as nsfw although it obviously is. I have tried attaching a screenshot but Jerboa throws an error. I have nsfw material turned off in my account settings, so this wouldn't happen if the post would be tagged properly. I'm using Jerboa. I could just ban the whole community but it is not the solution in looking for, because the ban works on app level and I have separate accounts for separate needs. Also banning the community is a reactory move and I would need to repeat that for every offending community in the future. That means that my feed would still be getting occasional nsfw material. Please advise.
lemmynsfw.com has a hard rule that all NSFW posts should be marked as NSFW. Report the post in question and instance admins or community moderators will deal with it. It shouldn't be a common issue.
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.
This was the same way this was dealt with in Reddit. Just report it.
The fact that I can't just block the entire instance is upsetting. I couldn't care less about people's butts.
+1, you should be able to block entire instances at the user-level like on Mastodon, we should not have to ask admins to block instances that bother a minority.
Definitely. I understand there are users who DO want that content, and they should be allowed to see it.
How long before a CP community pops up in our feeds though?
Using the Memmy app and had the problem. I found what had worked for me was going into settings on the actual browser and not through the app actually turned off the nfsw communities for me. If you haven’t tried that already I’d recommend giving it a shot.
Yep do this.
I don’t see nsfw
Technically I believe every communities created with the NSFW tag will auto-apply the NSFW tags on all posts. Maybe the user who posted submitted to a community that isn't tagged as such (some of them like /c/celebs@lemmynsfw.com) because the content is not always NSFW.
The only thing we can realistically do is to report these posts. It send a report to your instance admins, who can hide the post from being viewed at the instance you're at. It will also send a report to the mods of community at lemmynsfw.com in which the post was submitted who can take action on the post itself.
I think this is the issue - if the community itself isn't tagged, blocking NSFW on your account doesn't filter the posts (although they should be blurry if the posts themselves are tagged).
Fortunately, most of the untagged communities (inc. celebs) are modded by a user called Madness, so blocking him cleared up my feed.
This is more of a support question, please see the sidebar for suggestions on where to find support. Removing under rule #3.
Report the post and optionally block the user.
Off-topic but awesome avatar.
There was a post recently about NSFW tags possibly not federating properly, and I wonder if that might be what you're running into.
In terms of a real, solid solution, I don't know what the best course of action is. But as a band-aid solution, you could try an app that allows for in-app server blocking. Lemmy itself doesn't allow users to block an entire server, but Connect at least (and probably others) allow it on the app side. But it wouldn't help on anything other than the app, so it's definitely not the ideal solution.
Sounds like an issue with Jerboa more than with Lemmy tbh if you can't properly block a community. Log in to the website and block the community there.
Of course you can block communities in Jerboa. But not instances, as OP wrote. That just isn't a feature in Lemmy.
Blocking communities sucks because more and more pop up. I'd love to block the entire instance.
Connect has the ability to block instances.
It's the best app that I have tried so far to replace Relay for reddit.
If a community is marked NSFW, then all posts made in that community should automatically be marked as NSFW. Maybe even forced, so it can’t be unmarked.
Sometimes people simply forget to mark it NSFW. This would solve it.