Fediverse @lemmy.world ekZepp @lemmy.world 1y ago

Any chance to have a separated [PORN] tag to avoid blocking all kind of NSFW posts?

Many NSFW have nothing to do with porn. Sometimes are horror contents, some times are crude images, some times are just lazy people who don't know of the Spoiler tag. Can we have a quick and easy way to filter off all the (very funny but not alway wanted) Porn posts without locking out those other contents???

You're viewing a single thread.

61 comments

The tags are currently worked on, if you want to say something to make a change, write there.

https://github.com/Neshura87/Lemmy-RFC

Github issue that started the tags conversation. https://github.com/LemmyNet/lemmy/issues/317
- I don't think tags would be a solution as they wouldn't be standard threadiverse-wide. Also porn communities would want to mark their posts with specifying tags like every other community does instead of a generic porn tag.
  
  What's needed is expansion of the nsfw mark into subcategories
  
  there is proposal for three types of tags: NSFW, spoiler and generic. NSFW and spoiler will blur the images, and generic tags are for content categorization. NSFW and spoiler tags should have the same behavior on lemmy. kbin dev will want to make parity change for his feature.
  
  I still don't think it'd be enough to leave nsfw tag creation to communities. Even if a porn community created multiple tags under nsfw to classify their posts that would do nothing to help people block all porn on the platform. Porn, gore etc need to be their own tag types under the general nsfw type.
  
  We need parent and child tags. If we can create a parent 'porn' tag and a child 'hentai' tag nested, then people can block as wide or as narrow as they want.
  
  I would recommend you read the request for comment made by Neshura87, there he explained that it won't work like that. nsfw and spoiler tags are embedded into lemmy software.
  
  I read the thing, but that's still no reason not to seperate nsfw category further. It makes no mention of a technical limitation that prevents creation of more categories, it's just a person suggesting how a tag system could look like.
  
  there he explained that it won't work like that
  
  The entire reason I'm commenting is because I don't want it to work like that. I have no idea how to reply to a git commit, if I did I'd object there too.
  
  CW and NSFW are too broad to be the only 2 types of tags.
  
  The suggestion to use tag urls as ids don't work with the idea of using ids to share tags across instances. I don't want the entire threadiverse to decide https://lemmy.world/t/nsfw is the global nsfw tag and smaller instances being forced to use that or risk people facing unsolicited nsfw from their instance.
  
  There is no mention of filtering posts based on their tag category, which would make it impossible to block nsfw posts across instances without using the shared id. There needs to be platform level tag categories (especially for things people might not want to see) so content filtering works in a consistent and decentralised manner. Then individual instances or communities can create their their own tags based on those categories to fit their needs.
  
  The author seems to want to replace the spoiler mark with a (cw) tag called spoiler, but things can be both spoilers and fall under other tags (ie an image post, a leak, a discussion etc). Also this would pointlessly filter out regular spoiler content if a user blocks tags with the cw category.
  
  The way I'd want things is tags and spoilers / content warnings being completely seperate from each other at the platform level:
  
  Content warnings to let people filter out content they don't want to see. They wouldn't a content discovery tool. And they would be nestable. There would be platform wide default ones like
  
  Spoiler
  
  Nsfw
  
  Artful nudity
  
  Nudity
  
  Porn
  
  Shock
  
  Injury
  
  Gore
  
  Slurs
  
  . Users would be able to choose whether to show, blur or block content with these warnings in the settings. Instances and communities would be able to make their own content warning as well, managed by the user in the settings of a community. A user creating a post would see a menu to pick the content warnings (multiple if they want) that describe their post. Tags describe content to people who want to find such content. There could be generic platform wide ones like news, qna etc, but the majority would be community specific. Tags could also include default content warnings (eg 'leak' tag could activate the spoiler content warning).
  
  I think this would be the most elegant way to do it, but even what we have now feels better than what is proposed in that link
  
  @neshura@bookwormstory.social tagging the author.
  
  as I understand:
  
  we have 3 types of tags CW, NSFW and general type
  CW makes images blurred and text collapsed
  NSFW is the same as CW but you can opt in in setting to see all types of porn
  general tags are additional to tags above to specify content type: hentai, news, memes, etc.
  you can tag things with multiple general tags + CW or NSFW
  
  we won't have only lemmy.world/t/nsfw but also lemm.ee/t/nsfw and szmer.info/t/nsfw and this NSFW tags should be federated. All posts should appear the same if someone is following the same communities. Moderators can handle untagged content and tag accordingly.
  
  This is worth adding
  
  CW tag is based on activityPub protocol but author wants to split it on lemmy into CW and NSFW. On mastodon there is only CW for everything and #hashtags for specifying.
  
  Proposition is for different architecture
  
  NSFW for porn
  
  spoiler blurred not porn
  
  general for type content that is inside of a post: (nudity, hardcore porn, hentai, news, memes)
  
  Ability to choose which tags to show, which to hide is good addition. Automatic addition of CW for certain tags is also fine proposition.
  something worth exploring is same general tags that are federated across instances
  
  With #2, my problem was that without the ability to block categories, different instances would need to use the same shared id for the nsfw tag to let users block all nsfw at once; which is a regression from the current sceme.
  
  general tags are additional to tags above to specify content type
  
  So like hastags? I had assumed 1 tag per post
  
  Proposition is for different architecture
  
  Put that in there in case someone asks why I'm criticizing the current plan without providing an alternate one.
  
  Anyways, this scheme doesn't solve what op has asked for, which is to block porn posts platform wide without blocking all nsfw posts. With this scheme they'd need to add every community / instance's porn tag to their blacklist one by one, and it's not even guaranteed that posters would use the porn tag in addition to a more specific tag. Letting moderators set default tags for communities could solve the second problem. But to solve the first one either tags need to be blockable by name (instead of id) or there needs to be a seperate tag category for porn
  
  I think copying Mastodon would be the best for this. You can mark the post as sensitive (nsfw), which blurs the images. You can also add a content warning that can be used for anything (nsfw, nsfl, spoilers, etc).
  
  And then use tags separately for categorizing posts.
- Thank you I'll check the links 👍

61 comments