I recently was scrolling through my All feed and noticed some NSFW content on lemmynsfw.com. It was blurred but I wasn’t expecting it. What do you all think of this? Should we continue to federate with some NSFW instances? I’m personally OK with it as long as the content is blurred unless I click on it but wanted to get your opinions on it.
Edit: Completely forgot about the NSFW settings that everyone has. We’ll continue federating with NSFW instances going forward.
You must log in or register to comment.
I agree with most of the sentiment in these comments. Allow users to adjust filters & setting individually. Block individual users if they’re reported. Save defederating for hate speech, brigading, trolling, etc.
I think it’s OK as long as it’s tagged. Don’t really see the need to host it though, if there’s a difference on your end.
You can filter out NSFW content in your own account settings, so I see no reason to defederate from them.
I have hide adult content checked and I continue to see tons of nsfw stuff from lemmynsfw.
Then block those communities.
Pretty simple.
I’m here to replace reddit, so yeah I think I personally would like the option, even though I don’t usually look at NSFW.
in Bob Belcher voice “its the principle of it!”
I’m not from your instance, so take my opinion with a grain of salt, but I specifically looked for an instance that could access all the communities I want to take part in. You probably have users like that on your instance too, who would be sad or would even move to another instance if this were done after they joined.
In your settings, you can choose not to see any NSFW content. Similarly, when you’re not logged in on an instance, any NSFW content is hidden by default. While registering, it asks whether you want to see that, so I think you must’ve picked yes.
The main reason to defederate from instances with NSFW communities, as far as I’m aware, is that your instance will cache anything one of its users views from another instance. If that thing includes stuff that’s illegal in the instance’s jurisdiction, that’s a problem… Lemmy doesn’t even cache images, just the text, but that would contain a link to whatever content’s in the original post.
This is one reason why I chose midwest.social, that it federated with NSFW content. I vote let users control NSFW at their client level, and moderate NSFW content that isn’t correctly tagged.
I completely forgot about that NSFW setting. I thought it was just to automatically blur the image or not.
I just did a little test. With “show nsfw content” checked, images are blurred. With it unchecked, the post is not visible at all.
I’m less concerned with “NSFW or not” than with maintaining quality of discussions.
I’m pretty sure Lemmy provides settings to leave NSFW blur up to the user; isn’t that sufficient?
I’m ambivalent on the issue. I don’t plan to use this instance for NSFW content but I’m not opposed to it. Also, it’s your server, your call. There is an option to not display NSFW content in user profile settings so, as long as content is appropriately tagged, I don’t think it’s a problem.
if it’s blurred, you cant actually see it unless you click on it. I guess I dont see the problem
Defederation should be a last resort for problem instances. I don’t understand why so many people are suddenly so defederation-happy all of a sudden. Turn off NSFW content in your settings and just block any communities you don’t want to see. If it remains a problem down the line, then consider defederating.
When viewing new, I get a lot of posts from that instance that aren’t blurred… I’m not sure if it’s a tagging issue or a Jerboa issue, but it’s pretty obnoxious. I’m still generally supportive of keeping it around, but I hope they find a way to get that under control soon.
It’s a tagging issue. Essentially people are used to not having to tag posts in NSFW subreddits because they’re set to NSFW by default. That function doesn’t yet exist in Lemmy, so people are forgetting.
Actually, I just tested and it seems to be Jerboa. The same post behaves differently between desktop and Jerboa, unless it’s an app setting I’ve overlooked.
Weird. We’re going to have teething issues, that’s for sure.
I personally have no issue with it. So long as it’s properly marked (is marking as NSFW a thing in Lemmy?) I’d understand wanting to unfederate from a server that didn’t properly mark it though.
Yeah, it is. People forget sometimes, but the instances that allow NSFW are usually pretty strict on having all NSFW stuff be tagged, for federation’s sake.
Not gonna lie, off topic but this post is a great highlight of my biggest annoyance of this federation stuff.
You say “we” and “you all” in your post but I’m browsing from kbin and had to bother checking wtf “we” meant to see if it even affected me at all. So while I’m not part of the “you all” you address in your post, I’m here.
I just thing that people need to be way more mindful of their language to avoid confusion with all the federation stuff.
Does Kbin not label posts by what instance they come from? Jeroba (Lemmy Android app) will tell me which instance the post is from in the listing and I believe they’re planning to extend that to accounts.
I have a question about the potential legal problems. If I host my own instance and federate with a server that (like lemmynsfw.com for the sake of argument) allows NSFW content of drawn minors (or apparent minors, whatever, the details don’t matter), their content is copied onto my instance and I’m not hosting that content, right? So if that content is illegal in my home country, am I now hosting illegal content?
Not a lawyer. But I would say if the content exists on your host, even in a cache, you would be liable
That’s where I landed too. I’m tempted to run my own instance just for me to avoid hassle with defederations down the line, but it’s a no-brainer to block all nsfw content right now, the risk is crazy.
While I am not seeking NSFW content, I’m not offended by it. Nice to know I can adjust my own settings accordingly. ツ
would helpf if there were more advanced settings for what kind of content you want and from where
for example, only allow nsfw content from whitelisted instances or communities rather than having to rely on manually blacklisting them 1 by 1
