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???

  • @[email protected]
    link
    fedilink
    English
    2
    edit-2
    1 year ago

    @[email protected] tagging the author.

    as I understand:

    1. 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

    2. 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.

    3. This is worth adding

    4. 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.

    5. 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)
    6. 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

    • @[email protected]
      link
      fedilink
      English
      01 year ago

      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

      1. 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