Mastodon: CWs should not force a “NSFW” state

[KellerFuchs]

Setting a CW on a toot now seems to force the images to be hidden.

While _defaulting_ to hiding images is pretty sensible, forcing that state is

1. confusing, since users don't understand why clicking on the NSFW icon doesn't work;
2. actually unwanted in some cases.

For instance, when I post an image, I usually hide the description behind a CW, since it's mostly useful for sight-impaired people; now, my efforts at accessibility require me to be super-SPAMy :(

• [x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
• [x] This bug happens on a tagged release (v1.5.1, as running on vulpine.club)

[Cassolotl]

The discussion about this went on for a while, and here's the issue. Maybe this context will explain a bit why it is the way it is.

The CW thing is primarily intended to hide potentially harmful content. When CW and Hide Media were totally separate, people would click CW expecting it to hide the photo, and post the thing, and find that they'd posted a CW-worthy photo for all to see. So that's why this change was made - to make sure that photos that needed a CW were hidden.

Secondary things like hiding URLs or image descriptions are not the intended behaviour, and those would be covered by things like #117 and reverting to that thing that we used to have where image URLs were turned into tiny picture icons.

~

when I post an image, I usually hide the description behind a CW, since it's mostly useful for sight-impaired people; now, my efforts at accessibility require me to be super-SPAMy :(

This would be resolved by #117, which might be of interest to you? It's "Ability to add alt text to images/media" and it's been open for nearly 10 months but someone is slowly meandering towards a pull request. :)

[KellerFuchs]

@Cassolotl I'm not sure alt texts covers all use-cases, though they would be anyhow useful, and cover my specific example.

Also, it feels you misunderstood my report: defaulting to “NSFW” when setting a CW is sensible; the issue is with being unable to unset the image-hiding flag once a CW is set.
This shouldn't result in media not being tagged as hidden-by-default when it should, since it requires explicit user action to unset that tag after setting a CW.

[Cassolotl]

No worries, I thought some context might help but I was mistaken. :)

I am kind of wayyy in the other direction, I would rather have this:

I really dislike how unnecessarily complicated the whole Hide Media/CW situation is.