this post was submitted on 25 Jul 2023
68 points (100.0% liked)

/kbin meta

3 readers
12 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
 

I've seen several posts lately of people complaining about porn showing up in their feeds and the posters say that they don't want to block all nsfw posts because they follow other things, like news from the war in Ukraine, that gets tagged nsfw because of graphic imagery. I think they have a reasonable complaint and that the best solution is to separate the two types of content such that porn is tagged as nsfw (not safe for work) and graphic images/gore/non-sexual nudity ect are tagged nsfl (not safe for life). It may not be entirely fair to label non-sexual nudity, medical posts, and I'm sure many other categories that aren't jumping to mind right now as not safe for life but nsfl is an already established and generally recognized tag and I don't think there's any real advantage to having more than two tags.

you are viewing a single comment's thread
view the rest of the comments
[–] jon@kbin.social 4 points 1 year ago (1 children)

But there are things that would constitute NSFW that aren't porn and also not NSFL. I think a way to designate porn makes the most sense so you know whether you're clicking on a video of a bad car wreck or a video of a woman being raw dogged from behind.

[–] Can_you_change_your_username@kbin.social 2 points 1 year ago* (last edited 1 year ago) (1 children)

I addressed that at the end of my post for how I was thinking about it. I was using nsfl as a catchall for non porn nsfw because I didn't want to add lots of new tags, just have a porn and a not porn one. If porn moves to a new tag and everything else stays nsfw I wouldn't use nsfl, I'd go with akai's suggestion and just make the new tag be "porn" or something similar.

[–] blanketswithsmallpox@kbin.social 11 points 1 year ago* (last edited 1 year ago) (1 children)

How this is confusing people or purposely being obstinate is beyond me lol.

There REALLY should be two separate tags for content like you've said.

NSFW = Porn.

NSFL = Gore.

That's it lol.

[–] shepherd@kbin.social 4 points 1 year ago (1 children)

Just tagging things as Porn or Gore is a great idea! Let's mark stuff as what it is, not where it's... supposedly unsafe? lmao. Yes, you shouldn't be looking at porn while working, but there are plenty of non-work places where it's still not really appropriate.

I think there could be an argument for Gore being called like "Trauma" or something instead. Porn is broad, and I'd like another tag for "Viewer Beware" even if there isn't specifically Gore in it. A Gore tag feels more like a Sex tag, yes porn is sex but there's plenty of porn that isn't specifically sex.

[–] curiosityLynx@kglitch.social 4 points 1 year ago

Yeah, a nasty picture of gangrene would fit NSFL but not Gore. Same goes for so-called fail videos where, for example, a skateboarder fails to stick a landing and ends up with a railing between his legs.

I'd suggest the following tags:

  • Porn
  • NSFL
  • Triggers

All of which would automatically add a NSFW tag you can't add manually. Standard setting would be to hide all NSFW content (or whatever else the instance admin wants to set as default) and for each of these tags users could select hide/blur/show in the settings.