-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improvement upon labeling and UI for sensitive media and content #10
Comments
Just dropping a comment to note that this is still pretty relevant and good, even if the "NSFW" button has been replaced with an eyeball icon that helps a lot. Trying to keep old issues up to date! |
Since this issue was created, a number of things have been implemented:
Is there still work that needs to be done here? |
Would it be possible to have an instance-level setting that turns content warnings on by default, making them opt-out rather than opt-in? |
Corrects syntax for spoiler tags to valid HTML (fixes glitch-soc#10)
Closes glitch-soc#10 Co-authored-by: dean <[email protected]>
the CW and sensitive media features have some inherent flaws in UI and presentation/wording, and this list of proposed changes aims to address those.
NSFW is a term rooted in ableism and sex shaming, implying that sex work isn't work, and that work is the standard
as such, since CW is obviously the better term i would suggest these two feature be rolled into one, the CW feature aims to solve the same problem, but for text content.
this is not to say the ability to tag a post's image content alone, or text content alone, should be lost, and i would suggest this middle ground:
clicking the CW button should open a drop down below the toot box with a check box for "hide text" and "hide image" (only when images are attached, obviously)
since generally, you want both under a CW, these other use cases are smaller in size. by opening the CW drop down, you would hide both by default, and have a field to mark a tag for it. you may argue that this requires people to type the four letters "NSFW" to maintain the current feature, and to combat this i propose that empty content warnings still act like NSFW does now, visually, mark it as "hidden" in general, and display "tag not set" before the show more button
thanks for listening.
The text was updated successfully, but these errors were encountered: