@Leon Cowle @Stefan Bohacek Yes, that's the trouble with CW policing: People don't police CWs in general. They often don't just police the obvious CWs for porn and gore either. Instead, they aim to enforce all the CWs which they personally need. Regardless of what someone else may or may not need. Then you comply, and then someone else comes and berates or even sanctions you for using too many and/or completely superfluous CWs.

I've compiled a list with over 140 topics that someone demanded be CW'd at some point. And it's very incomplete because it should technically include politics from not only every last nation on the planet, but also every last federal state, province etc.

The worst offenders are those overly sensitive snowflakes who probably came over from Tumblr, and who present themselves as so easily triggered that they absolutely need literally everything CW'd. And as so feeble that they cannot take care of protecting themselves in any way. Granted, I think it'd be too much for them to set up hundreds or thousands of individual filters, especially what with how unnecessarily complex Mastodon's filters are. But still, they see themselves as entitled enough to demand everyone force CWs for everything on everyone, regardless of who needs CWs for what, because they need CWs for everything.

#Long #LongPost #CWLong #CWLongPost #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Filter #Filters #Mastodon #MastodonCulture #Hubzilla

@David Tanner 🏴󠁧󠁢󠁷󠁬󠁳󠁿 @Stefan Bohacek You don't. You don't apply them to stuff that you send to others. You apply them to stuff that you receive in your timeline. Not for others, but for yourself.

I think the issue here is that it's often hard-wired in Mastodon users' heads that "CW" equals "poster-side" equals "provided by the poster for all readers all the same".

In this case, it's different. It's all happening on the reader's side. Like, the filter generates a CW for the reader who sets up the filter, depending on what keywords the filter contains, depending on what keywords are in a post.

You, as the reader, define what you want to have hidden behind CWs for yourself. If something disturbs you just enough to have it hidden, but not enough to have it purged from your timeline entirely, you set up a filter with the corresponding keywords. And that filter will hide content with at least one of these keywords in it behind a CW. Automatically generated only for you, personally, individually.

The next user does not want the same content hidden. They do not set up such a filter. And they see the very same post without a CW without having to do anything themselves.

I mean, I guess you know what filters do on Mastodon. Normally, they remove stuff from your timeline. But with this setting, they hide that content behind a button for you instead of completely removing it.

Maybe it's easier to understand for us Hubzilla users because we've had something similar since before Mastodon was even made, much less since before Mastodon started repurposing our summary field for poster-issued CWs. So automatically generated, individual, reader-side CWs are the default for us and part of our culture whereas they came to Mastodon too late to become part of Mastodon's culture.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Filter #Filters #Mastodon #MastodonCulture #Hubzilla

@zotheca @Stefan Bohacek It isn't the title field. It's the summary field. It has been the summary field since Evan Prodromou added it to Identi.ca in 2008. And it only became a CW field when a Mastodon user for the demo scene submitted a merge request to Mastodon's GitHub repository in 2017 which repurposed this summary field, unused by Mastodon at this point, as a CW field.

My own POV on this is a whole lot different from typical Mastodon POVs. I've joined the Fediverse on Friendica in the early 2010s as opposed to on Mastodon in the 2020s before I moved on to fledgling Hubzilla.

Now, both Friendica and Hubzilla as well as the whole rest of the family (of which (streams) of 2021 and Forte of 2024 still exist) have a nifty optional feature called "NSFW": It's a list of keywords which, if detected in a message, hide the entire message behind a button. Much like the hiding feature in Mastodon's filters, only not built into the actual filters, much more simple and over 12 years older than Mastodon's solution.

In this software family, the NSFW feature is not perceived as a filter, even though it's very similar to the actual channel-wide filters (which, by the way, are among the few things which are more simple even on Hubzilla than on Mastodon because they've only got two keyword lists, an allowlist and a blocklist).

Rather, it's seen as an automated, individual, reader-side CW generator. It's deeply engrained into the culture of these Fediverse server applications which is a great deal different from Mastodon's culture. And it's seen as vastly superior to poster-side CWs that are forced upon all readers all the same.

A takeaway from this software family: If you write a potentially sensitive post, and you have no way of artificially weaving NSFW-triggering keywords into the actual post text, add them to the bottom line as hashtags. I do that all the time, hence the hashtags that start with "CW" to make clear that they're supposed to trigger reader-side CW generators.

By the way, the Friendica and Hubzilla inventor and (streams) developer Mike Macgirvin proposed two catch-all hashtags for sensitive posts to the (streams) users (that was before he forked Forte off the streams repository). One is #sensitive which also has the side-effect that (streams) and potentially also Forte make Mastodon blank out all images in the post. The other one is #⚠️. Or, if your post is really disturbing, #⚠️⚠️⚠️⚠️⚠️. However, this has yet to find its way into Hubzilla, not to mention Friendica or even Mastodon and the rest of the Fediverse.

As for the summary field, if Mastodon actually managed to push its entire community away from fixed poster-side CWs towards automated reader-side CWs, the whole field would be useless. I mean, Mastodon didn't support it at all before it had a CW field because, frankly, you don't need summaries for 500 characters.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Filter #Filters #Mastodon #MastodonCulture #Friendica #Hubzilla #Streams #(streams) #Forte

@Stefan Bohacek This is the case for three reasons.

One, Twitter has never had this feature. And if Twitter doesn't have a feature, it's hard for many to imagine that Mastodon has it.

Two, there is no dedicated button for it up-front in the timeline view, neither on Mastodon's Web interface nor in any mobile app.

Three, it came too late. Mastodon's culture as we know it now was coined in spring 2022 by those who had escaped from Twitter after Elon Musk had announced he wanted to buy it. However, this filter feature was introduced to Mastodon with version 4.0 in October when Mastodon's culture was already set in stone for all eternity.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Filter #Filters #Mastodon #MastodonCulture

@⚝ Mirko ⚝ die Adminbubble dort ist sehr viel ausgeglichener und lässt vor allem andere Plattformen in Ruhe.
Mindestens die Hälfte von denen weiß doch gar nicht, daß es auch noch andere Fediverse-Serveranwendungen gibt. Für die ist das Fediverse gleich Mastodon. Und von denen, die das wissen, wissen die allermeisten nicht, was die anderen Anwendungen können.

Warum hat die "Mastodon-Community" beispielsweise nie gefordert, Pleroma, Akkoma, Misskey, die Forkeys, Friendica, Hubzilla usw. zu deföderieren, weil die alle in der Lage sind, jeden öffentlichen Mastodon-Tröt widerstandslos zu quote-posten? Weil auf Mastodon praktisch niemand weiß, daß die dazu in der Lage sind. Wüßten die das, hätten sie längst die Messer gewetzt und die totale Deföderation gefordert.

Außerdem wird man auf diesen Serveranwendungen immer wieder von Mastodon-Nutzern diskriminiert oder gar attackiert. Man soll sich gefälligst an die "Fediverse-Kultur", will sagen, Mastodon-Kultur halten (was impliziert, daß man die eigene Kultur über Bord werfen soll). Man soll niemals mehr als 500 Zeichen posten. Man soll "alle notwendigen" CWs ins CW-Feld eintragen (also Friendicas Abstrakt-Feld bzw. Hubzillas Zusammenfassungsfeld) und es gar keinen Fall für irgendetwas anderes benutzen. Und so weiter.

Derweil beharren praktisch alle Mastodon-Nutzer darauf, daß das nie passiert. Weil sie nie mitbekommen, daß das passiert. Ihnen selbst passiert es ja nicht, weil sie sich als Mastodon-Nutzer eh an die Mastodon-Kultur halten, eh nicht mehr als 500 Zeichen haben, das CW-Feld nur als CW-Feld kennen usw. Und wenn es ihnen nicht passiert, dann sind sie der felsenfesten Überzeugung, daß es gar nicht passiert.

Das Nicht-Mastodon-Fediverse widersetzt sich ständig Mastodons Kultur und bricht ständig Mastodons ungeschriebene Regeln. Die allermeisten Mastodon-Nutzer wissen aber nicht, daß das passiert, ganz einfach, weil sie davon nichts mitbekommen. Dasselbe gilt auch für die allermeisten Mastodon-Admins.

Mastodon stellt im Fediverse irgendwo zwischen 60 und 70% der monatlich aktiven Nutzer. Aus irgendwelchen Gründen aber kommen gefühlt über 98% des Post-Aufkommens auf Mastodon von Mastodon selbst. Du kannst 4 Jahre auf Mastodon sein, 1000 Konten folgen und dich trotzdem in einer reinen Vanilla-Mastodon-Blase bewegen und erst nach diesen 4 Jahren deinen allerersten Beitrag mit über 500 Zeichen zu Gesicht bekommen. Wenn überhaupt.

Mastodon-Admins sind gegenüber dem Rest des Fediverse nicht deshalb so entspannt, weil das, was Pleroma, Misskey, Friendica usw. nach Mastodon schicken, für sie okay ist. Sondern, weil sie gar nicht wissen, was Pleroma, Misskey, Friendica usw. nach Mastodon schicken und viele von denen nie auch nur irgendwas von diesen anderen Anwendungen gehört haben. Sonst wären tausende von denen an vorderster Front mit dabei, wenn es darum geht, alles, was nicht Mastodon ist, auf Mastodon zu blockieren, das kannst du mir mal glauben.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteTröt #QuoteTröts #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebatte #QuoteTrötDebatte #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #ZeichenLimit #Zeichenlimits #ZeichenlimitMeta #CWZeichenlimitMeta #Fediverse #Mastodon #NichtNurMastodon #FediverseKultur #MastodonKultur #MastodonRegeln

(🤍, ⚡, 💜, ❤️‍🔥) If your post is about:

- the politics of a government that exists today on Earth (i.e. in real life), use <region/regions> politics; as a pro-tip: try to not use a region's two-letter or three-letter code/abbreviation (example: is ID politics about politics in Idaho or Indonesia?).
- a well-known person or group of well-known people who are harmful to others (ex. they are transmisic, queermisic, racist, ableist, fascist, etc.), regardless of if they are passive-aggressive or actively, forcefully hostile (or anywhere in between), put their name(s) in the content warning, and do not redact it/them.
- queermisia, transmisia, racism, ableism, or any other kind of hate against others (and not advocating for it), content warn it as queermisia, transmisia, racism, ableism, etc.
- a current event that anyone could miss out on, content warn it as <name or type of current event> (example: 39c3 for 39C3 or meetup for a local meetup).
- a current event in general, content warn it as current events.
- about food, content warn it as food; content warnings such as meat, vegan, processed, etc. help indicate the post is about meat, vegan food, processed food, etc.
- anything that can be overstimulating (e.g. has a video or audio recording of something loud, a video or gif with flashing lights, a video or gif with fast moving objects, etc.), use loud, flashing lights, fast-moving objects, etc.
- anything sexually suggestive, content warn it as suggestive, mildly lewd, NSFW.
- anything sexually explicit, you must definitely content warn it; possible content warnings include sex, lewd, NSFW.
- about kinks (in sexual/erotic contexts) or kink equipment, content warn it as the kind of kink(s) it is about (example: pet-play, bondage, BDSM, etc.).
- about or related to gorey topics, whether actual or depictions of gore or violence, use gore, blood, sharp objects, firearms, etc. Note: your mileage will definitely vary on what you can post about if it is about gore and violence.

This is all we can think of right now, but we will reply to this if we think of anything else.

#ContentWarnings