So, a lot of features are coming next update to help alleviate some of the annoyance of federating with NSFW instances.
For context, I defederated from the NSFW instances because they clutter the absolute FUCK out of /all. I mainly anticipated federating with them in time when it could be hidden from /all, but domain blocks seem to be coming next update at least as well as disabling remote image caching.
Would yall be ok if I refederated? Or should we wait a bit more for community silencing and hiding as well.
I’d prefer to wait a bit until more clients implement the nsfw features. That’s just me though
Yeah, I think having more granular federation options would be helpful as well. I would really really like a way of silencing from /all. So people who want some boobs and butts can find them if they really want to.
As long as there’s a way to block specific ones/all of them I’d rather have the option to see them
Well my reply is possibly ironic as I am literally sitting here wearing a tshirt that says
“Banned books are the best books”
But…
I’d only do so if you’re confident that you have the tools to manage it. I have zero problem with porn, but given the wildly divergent fetishes that exist, I definitely would prefer it wasn’t it in my feed by default. Happy for it to be available for anyone to subscribe to of course.
I am of course not the admin, that’s merely my 2bob’s worth. Your call.
I’ve moved to a client (sync) which has very extensive filtering options so theoretically I can filter out pretty much anything, so personal impact is theoretically low.
As a side anecdote I reacted to a query on the sync for lemmy sub about not being able to see NSFW lemmy feeds by looking there in anonymous mode in the app (to test if it was the app or not). I noped out kinda fast (and cleared the cache for good measure)
Yeah, so make sure you have good admin tools
Is there a universal definition of NSFW? I can imagine instances that would call beach scenes NSFW where less conservative groups would have no problem with them. It changes the calculus, IMO.
What’s your take on the question?
Porn.
I remember particularly gory news feeds also being NSFW, so it’s not only porn and erotica that can fall under that tag.
Are the NSFW tags given by the author of the post? Then the benchmark is going to be different depending on the poster: from naked boobs being tagged to more explicit content not being considered NSFW.
I am personally happy with not seeing NSFW content, I come here for books, memes and political discussion, I would hide NSFW posts asap anyway.
I didn’t see your second response I am a silly goose. I think it’s very much worth waiting, I have no issue with 18+ content but I don’t want it to spam the hell out of /all. Like if there was a way to silence it from /all and make it follower only I would be fine with it
I agree with that position. Hopefully, those tools are on the roadmap. Maybe until they arrive, holding federation would be a good move. Anyone who feels strongly about it can create an account on the instance they want to subscribe to.
Porn is NSFW, I agree. But most erotica is also NSFW. Even some simple photos of shirtless guys or women in bikinis are NSFW, depending on context. It becomes difficult to draw the line. Then consider that we don’t have a universally agreed definition of “porn,” and we’re deep into the weeds.
Basically pornography, like sexual depictions of boobs and butts and genitalia is where I’m gauging from
A good standard :)
Lemmy already hides NSFW content by default, with an option to enable it in the user settings. The upcoming feature to block instances sounds great, but even without it, I have not had issues with NSFW content on my /all feed. I’m new here but I’ve been using a different instance with a very open federation policy, and the worst I get in /all is non-nude celebrity pics, and it’s not a ton.
Is your experience that NSFW instances clutter /all with posts that are not tagged as NSFW?
I think it’s fine to federate with any server that has good administration and moderation.
Anyway, I think you are approaching this correctly, and I see no harm in waiting a little longer to see how the new features play out in practice. It sounds like clients will all need to be updated for lemmy 0.19.
