@Lotte Issues with mandated CW policies
Cautionary trigger warnings can be written at the head of toots. I've no objection to doing so.
Trigger: this toot discusses CWs.
CWs are often used as subject lines. They're not that. (You've done so here.) A title can be included in a post directly. Clients supporting Markdown (e.g., Glitch.soc) enable bolded titles or even multiple header levels.
Requests for use of CWs are arbitrary, conflicting, and very often stated as absolutes. For any convention in which voluntary compliance is sought, these practices tend to increase rather than decrease frictions.
CWs do in fact pose real access and usability issues, a fact which is persistently ignored and derided when raised in discussions. Longstanding requests to address these limitations have been ignore by Mastodon developers.
There are other tools which provide for a filtered experience, inclusing keyword/hashtag filters, Lists, and controls limiting visibility of boosts, as well as mute and block features.
These aren't uniformly available, and may be lossy. As tools for preserving overall civility and concord among the Mastodon / Fediverse community, they're probably better than moral outrage and brigading attacks.
Outside a fairly limited set of very broadly accepted standards (sexual content, nudity, gore, NSFW/NSFL imagery), spoilers in popular entertainment, jokes/puzzles, CWs actively cause extensive problems. I can sympathise strnogly with being sensitive to types of content (I am), but the answer for non-directed exposure is to exercise (and request stronger/better) filters, not to bend the rest of the world to often-conflicting, contradictory, and themselves prejudicial self-censoring obligations.
Note that I strongly contrast incidental exposure (something in the stream, or boosted generally, with targeted exposure, where a person is specifically tagged. Brigading attacks especially are simply abuse.
TL;DR: No. Your proposal fails to recognise the many side effects and consequences of CWs.
cc: @woozle
#cw #cws #filtering #CommunityPolicy #accessibility #usability #fairness #CodeOfConduct