68
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Jul 2023
68 points (100.0% liked)
/kbin meta
8 readers
2 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
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.
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.
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:
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.