Just throwing a thought out there, I keep NSFW enabled/blurred on the webUI because folks tag things that way which are maybe with blood or similar (think a war photo). But I'd love to not see the "Rear Pussy" community trending in Hot when I wake up. Call me crazy. edit: added enabled/blurred for clarity, I use click-to-see depending on the content. I've learned.

you are viewing a single comment's thread
view the rest of the comments
[–] 28 points 21 hours ago (8 children)

I call You crazy. You\re welcome. /s

Sometimes, I feel like we (whole internet, not just Lemmy) could get sub-tags of nsfw, that we could switch on and off independently. nsfw-gore, nsfw-porn, nsfw-textonly, nsfw-medical, nsfw-disgusting, nsfw-violenve, even nsfw-meme... Would want some in, and totally disable others. As often nsfw tag is overused, means content is totally unknown.

  • source
  • hideshow 8 child comments
  • [–] 7 points 20 hours ago* (7 children)

    I see cw (content warning) with a descriptor fairly often, perhaps that's something to lean into. Also just blocking egregious communities works wonders.

  • source
  • parent
  • hideshow 7 child comments
  • [–] [S] 4 points 19 hours ago (6 children)

    The issue mentally with this approach (which of course I use) is that I had to be exposed to the Rear Pussy community in my morning feed in order to block it. And opening the /c/ to click the button treated me to... what the subject is about in full pixel detail. I'd rather just not, you know?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 9 points 19 hours ago (4 children)

    Seems like more of a UI issue in your reader tbh. In Boost I can just mute the post/user/instance/community directly without opening it. And I don't even mind the NSFW communities. I just dislike and mute those users that spam the crap out of them.

  • source
  • parent
  • hideshow 4 child comments