this post was submitted on 14 Jun 2023
15 points (100.0% liked)

Asklemmy

44153 readers
1147 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 3 points 2 years ago

I always thought that NSFW was too vague a term. One person's NSFW is different to another's.

What would work better is specific content tags. That would work well for trigger warnings too.

It would cover porn: nudity, softcore, hardcore

But also content themes: Alcoholism, drug taking, violence, suicide, war, guns

It could even be used for spoilers.

Users could then select the specific themes they didn't want to see. For better UX you could have a slider that had pre selected levels. "strict", "relaxed", "everything".

Posts often present content warnings behind spoiler tags at the start. The idea being that some users don't want the story spoiled by hearing what themes it contains. That's why I believe this system would work. Rather than having the content warnings visible it all happens in the background through structured data. Your app already knows if it's content you don't want to see so it either hides it, or perhaps blurs it with a warning that you likely don't want to read it.