Hi, I was just browsing kbin on my work pc which is not signed into my account. While scrolling down there was a very nsfw picture (female genitalia) in the random posts sidebar. This nsfw content was, for some reason, not even blurred. I’ve seen this a couple times previously and am not sure where a good place to report or request a feature request is?
NSFW content doesn’t even show up anywhere for me in kbin - unless I go directly to the magazine/community. I have everything set to allow it to show, but it just won’t. I don’t understand how y’all are getting random tidbits of titties without trying, but it seems to be actively censored for me.
It also shows post from things I blocked like disturbing news. It would be nice to be able to disable this random post feature completely.
I’ve been getting this too, even though nsfw content is supposed to be filtered for me. I also sometimes see straight up nudes in the microblog as well. Either something is not working correctly, or the nsfw filter only works for the threads so far.
NSFW filtering was supposedly fixed a month ago, but it either isn’t working or the instance hasn’t updated to the latest changes yet.
As a workaround, I’ve been hiding the sections with a uBlock Origin filter.
Just add these lines to the “My filters” page in uBlock Origin. The first line hides the “Random Posts” section, and the second line hides the “Random Threads” section. (Replace “kbin.social” if you’re on a different instance)
kbin.social##.section.posts
kbin.social##.section.entries
I also hide the “Active Users” and “Related Magazines” sections.
kbin.social##.active-users.section
kbin.social##.related-magazines.section.magazines
This is a good fix, for a super clean kbin i added the following to ublock:
kbin.social##.section.posts
kbin.social##.section.entries
kbin.social##.active-users.section
kbin.social##.related-magazines.section.magazines
kbin.social##.kbin-promo.section--no-bg.section
Probably the user forgot to check the nsfw flag/checkmark.
It’s easy to report posts on Lemmy, at least via liftoff which is mostly what I use.
