There’s a few NSFW communities who keep getting advertised on the sidebar, showing an inappropriate photo. I don’t care to see it.
I’d suggest that the right way to handle this is, if the “Hide adult content” checkbox under settings is checked, it should prevent this from happening. (Currently it makes no difference, afaict.)
I believe it does make a difference. It just seems like nobody cares to turn on the nsfw filter
It only makes a difference if people are properly labelling content and communities.
Yep this is the answer. I have the filter turned on and it most definitely doesn’t work since all those posts are untagged.
I thought it was on by default, I have a (possibly confabulated) memory of unchecking it because I want adult content to show up; I prefer a more true to humanity face on the internet, that includes us at our shaking it baby, banging like it’ll solve global hunger, nude lewd and crude finest.
Sorry, I meant that people making nsfw posts are the ones who don’t turn on the nsfw tag on their posts.
But yeah, the nsfw filter is off by default on people’s accounts
I’ve noticed the vast majority of it coming from lemmynsfw.com
I really hope that we can get the ability to make entire instances (and thus all posts in any of their communities) as nsfw, since that already is an explicitly and exclusively nsfw instanceI’ve blocked their entire domain and I now I don’t see their NSFW posts anymore.
Go to https://kbin.social/d/lemmynsfw.com (basically `/d/<domain you want to block>') and press the block icon on the sidebar. Yes you’ll have to briefly look at their front page before you can block their content.
Actually, comparing notes a bit, it seems like sometimes posts are marked as nsfw on the server they are from, but show up as sfw on our side. There’s definitely some sort of bug going on here.
I have been seeing this as someone who’s posted NSFW content. People from other instances will hit me up to complain about it when I’ve done what I can by posting on a NSFW server and marking it NSFW…
Right. I was on the opposite side on this, as I was giving someone a friendly reminder about marking a post nsfw, but we compared screenshots, and it clearly was marked as NSFW on theirs and not mine, and the same was true for several other posts.
Ah, yeah. Definitely in favor of people marking things correctly. While misfiling is also very human, you gotta draw a line somewhere, and given that this particular case fucks up on people’s consent to exposure, it seems like a pretty good place for it.
I won’t go back to mastodon because I opened the app to a huge picture of a wang, and I do NOT want that content, so I have the settings set to block it. It wasn’t blurred, or hidden behind a “click to reveal” button. Just wide open, filling my entire screen. And I had to keep seeing it to check if it was tagged nsfw, and to click to report.
Good lord theres penise
ThatsMyFetish.gif
That sounds really unfortunate, and I am sorrowful that you had that experience.
I would hope that moderation starts kicking in on that kind of thing.
I know Beehaw’s recent defederation ruckus wasn’t popular, but it does highlight the importance of moderation tools. If I was running an instance I’d want to be able to see stats for how often that kind of thing gets caught, and perhaps if there are instances that it happens on a lot then defederation would be warranted. People need to keep their portions of the neighborhood tidy.
a thing with the nsfw filter in the fediverse generally: there is a school of thought that people should treat “content warning” somewhat like an email subject line - basically marking everything nsfw if there is any chance that anyone might find it offensive. Not subscribing to that point of view myself, I tend to block anyone I encounter who adopts that practice because it is so annoying - but I can also understand that some people of very delicate sensibilities might appreciate being able to protect themselves from things that are not well-behaved kittens. TLDR, this is why a lot of people don’t turn on their nsfw filter - because in many places 90% of the so-called nsfw content is actually sfw, but evokes food, alcohol, politics, violence (yet of the sfw sort), or controversy.
It does not make a difference.
It’s a good temporary solution but not perfect. I personally like some NSFW art (and people often mark pretty innocent stuff like memes as NSFW too, just to be on the safe side) but then again I don’t want random gaping buttholes on the front page either. Additionally, plenty of porn isn’t marked as NSFW at all although the instance-wide setting that ernest recently added should help with that I hope.
Personally I blocked the whole nsfw domain and then hid the random posts and threads div with uBlock (just right click the area. slide the sliders until it surrounds what you want to remove and then confirm) for now.
They can also be posts from communities you’ve already blocked while curating your kbin experience, which is a downer.
Honestly, the whole “random stuff” sidebar seems to be unnecessary.
This … please just let us disabled random stuff. I assume there’s some theory about broadening people’s exposure to help subs grow but it’s really just annoying at the moment. I’d rather have that screen space back.
The issue tracker has open issue for this:
https://codeberg.org/Kbin/kbin-core/issues/118#I’d like to totally disable the sidebar. I don’t need random posts, especially if it’s this kinda stuff I don’t want to see.
I blocked the random crap using Ublock Origin. You can use the ublock picker tool to select the section of the page you’d like to hide.
Been using it forever and didn’t know it could do this. Definitely a better option for anyone that doesn’t need stylus for something else.
As a temp workaround, add the following css in stylus or stylbot for kbin.social to hide random posts and threads
section.posts.section {
display: none;
}section.entries.section {
display: none;
}improved version:
section.active-users.section, section.posts.section, section.entries.section { display: none; }and my favorite (makes screen wider) -
.kbin-container { max-width: 90%; }
problem is it also comes up in /all. which is the default landing page. So yeh, you have to reactively block communities, which still leaves you open to exposure unfortunately - lemmynsfw will certainly not be the last nsfw instance. not particularly nice when you’re just browsing /all when family walk in the room and there’s several thumbnails of females in compromising positions on your screen.
A lot of the posts are coming from lemmynsfw.com, which is a domain you can block. Unfortunately you have to navigate to their Kbin domain page, but you should be able to block them completely there.
I think it’s something like kbin.social/d/lemmynsfw.com, and you just block it like a magazine or a user.
Definitely wishing there was a way to block without having to navigate there, you’re definitely in for an eyefull
Blocked domains, communities, and users currently show up in the side bar.
The sidebar is pretty broken at the moment, yes
Dang that’s no good at all
it’s a very literal interpretation of random
Not OP, but domain blocking doesn’t seem to be working at the moment (at least for me). I ended up searching “nsfw” in magazines and blocking from there individually. That method seems to work, but it’s also kind of a never-ending process, as other NSFW magazines start showing up as people sub to them. I’m sure it’ll get sorted eventually.
Yeah, I kind of agree. I really don’t need to be hit with the Vadge-o-Matic the moment I open the site.
For science only, I would like to have the chance to understand wherever you folks seem to get these nfsw content on your main page (or sidebar? I don’t even know where that exists)
Please, please help me avoid such content by telling me where to find it so then I can never go there and only understand better in what framework such content would exist
Honestly, I don’t get any of this on my main (Local) feed
Please, please help me avoid such content by telling me where to find it
Most of it is from lemmynsfw instance (it’s not flagged NSFW because it doesn’t have to).
Honestly, I don’t get any of this on my main (Local) feed
Yeah, you wouldn’t. It’s federated content.
