Netzgemeinde Hubzilla
Anmelden
Registrieren
Netzgemeinde Hubzilla
Anmelden
Registrieren
System Apps
Fehler melden
Hilfe
QRator
Sprache
Suche
Verzeichnis
Zufälliger Kanal
2026-05-12 20:49:11
Profil ansehen
Stefan Bohacek
stefan@stefanbohacek.online
nsfw - ansehen
Applauding
@admin
for taking a strong, well-argued stand on this.
Can we get more admins onboard?
#fediverse
#FediAdmins
#MastoAdmins
1
Screenshot of a Mastodon server's server rules: Don’t police others’ use of CWs, alt text, or tags Whilst we have some guidelines around when to use CWs, alt text, and tags, we only have one rule about them: Use CWs for adult or NSFW content. You can politely ask other people to use specific CWs, alt text, or tags that you prefer, as long as you don’t state your preferences as absolute rules or requirements. This is especially important when marginalised people speak about their experiences of marginalisation. For example, if you are not BIPOC, don’t tell BIPOC to hide their experiences of racism behind CWs.
Link zur Quelle
2026-05-12 21:03:06
Profil ansehen
Stefan Bohacek
stefan@stefanbohacek.online
And just to clarify, this is less about specific rules around CWs/alt text and more about having those rules in writing, and making their enforcement the responsibility of moderators.
2
Link zur Quelle
Expand Replies
2026-05-12 22:29:09
Profil ansehen
The Socel Director
admin@socel.net
@stefan
@admin@blorbo.social
I was there during the twitter migration, and saw some very immature shaming of newcommers not using Alt and CWs. Which prob gave the fedi a reputation that may still persist, with some that left.
From that, I took the lesson that you cant scold or require these things. Ppl will leave. It's also not respectful to a fellow-human stranger.
Now, they are not bad ideas. And there is far more value in -building- their cause. Than tearing down a person who's iffy to them.
1
Link zur Quelle
Expand Replies
2026-05-12 22:29:54
Profil ansehen
Texan_Reverend
Texan_Reverend@kind.social
nsfw - ansehen
@stefan
@admin
Kind.Social has had this included in our server rules for years now.
While we encourage CWs and alt text, it runs entirely counter to accessibility and decency to police or bully people over them.
(Again, with the exception of NSFW/harm.)
Link zur Quelle
2026-05-12 23:55:43
Profil ansehen
Karl Voit :emacs: :orgmode:
publicvoit@graz.social
contentwarning - ansehen
@stefan
@admin
I once wrote
https://karl-voit.at/2022/06/05/mastodon-cw-misuse/
which adds some aspects to the discussion on CWs.
YMMV
#publicvoit
#contentwarning
#CWs
#CW
Link zur Quelle
2026-05-13 01:07:05
Profil ansehen
Jupiter Rowland
jupiter_rowland@hub.netzgemeinde.eu
contentwarning - ansehen
@
Stefan Bohacek
@
Blorbo Admin Chicken
Yes, I wish more servers had this rule and enforced it.
Officially appointed moderators only go by the server's written rules, and they only enforce them against local users.
The HOA, on the other hand, have some rules in their heads. Everyone has different rules. And they enforce them against
everyone
, even regardless of where everyone actually is. Like, they attack Friendica users for allegedly misusing the CW field because they neither know that these users are not on Mastodon, much less where they actually are, nor that Mastodon's CW field has been an abstract field on Friendica for seven years longer than it has been a CW field on Mastodon.
This is part of what makes the Fediverse a minefield once your messages start reaching Mastodon.
I can't say that I'll stop being so overly careful with everything and putting such a big effort particulary into image descriptions, summaries/content warnings and hashtags for filter-triggering purposes if more or even most Mastodon servers adopt and enforce this rule. The irony is that this rule actually protects my long hashtag lines.
In fact, rules like these also ought to include that nobody must be policed for writing "too long" posts because there are places in the Fediverse that neither have character limits to worry about nor a character-limiting culture.
#
Long
#
LongPost
#
CWLong
#
CWLongPost
#
FediMeta
#
FediverseMeta
#
CWFediMeta
#
CWFediverseMeta
#
CW
#
CWs
#
CWMeta
#
ContentWarning
#
ContentWarnings
#
ContentWarningMeta
#
AltText
#
AltTextMeta
#
CWAltTextMeta
#
ImageDescription
#
ImageDescriptions
#
ImageDescriptionMeta
#
CWImageDescriptionMeta
#
Hashtag
#
Hashtags
#
HashtagMeta
#
CWHashtagMeta
#
CharacterLimit
#
CharacterLimits
#
CharacterLimitMeta
#
CWCharacterLimitMeta
Link zur Quelle
2026-05-13 02:49:44
Profil ansehen
Sean C.
filmfreak75@mastodon.social
@stefan
been subjected to CW policing re general political content once…
…was not a productive exchange
@admin
@developerjustin
1
Link zur Quelle
Expand Replies
2026-05-13 09:21:11
Profil ansehen
Jupiter Rowland
jupiter_rowland@hub.netzgemeinde.eu
contentwarning - ansehen
@
Sean C.
@
Stefan Bohacek
@
Blorbo Admin Chicken
@
Justin Ferrell
I've once encountered someone who seemed to suffer from such extreme PTSD that they
demanded everyone CW literally absolutely everything
. And, of course, the Mastodon way by
forciing all these CWs upon absolutely everyone all the same
.
Now, I'm not even on Mastodon myself. I'm on Hubzilla which is doing CWs way differently from Mastodon, which has been doing that for longer than Mastodon has even existed, much less has had CWs.
We don't do CWs poster-side. We don't write CWs into the summary field. In fact, the summary field, which Mastodon has been using as a CW field since 2017, is still a summary field here. A summary field makes a whole lot of sense here, for while most Mastodon servers have a hard-coded character limit of 500, Hubzilla doesn't really have any character limit at all.
Also, we can't do Mastodon-style CWs in replies which are called "comments" here. Like on Facebook, like on Tumblr, like on every last blog out there, but very much unlike on Mastodon, our post editor and our comment editors are wholly separate things. The comment editor can't do summaries. Why not? Because, have you ever seen a blog comment with a summary?
No, we have our CWs automatically generated and reader-side. We have a kind of filter called "NSFW" that can automatically hide content behind a CW. It's basically Mastodon's "Hide with a warning", but as its own keyword filter list and seven years before Mastodon introduced "Hide with a warning". (Twelve years actually because Hubzilla inherited that feature from Friendica.)
When we post sensitive or disturbing content, we make sure that those who may not want to see that content have their filters triggered. We do so by making sure that appropriate keywords are in the post text (easy-peasy when you can post over 33,000 times more characters than on Mastodon) or by adding hashtags. The latter is what I do, hence the many hashtags down there.
It's also the only way to have a
comment
hidden. Again, Hubzilla doesn't have a summary field (= Mastodon CW field) for replies, so it has to rely on people making filters for uncomfortable content.
This could be a thing on Mastodon as well. After all, in October, 2022, Mastodon 4.0 introduced "Hide with a warning" to its filters which does the exact same thing as NSFW on Friendica and Hubzilla: hide messages depending on keywords. However, Mastodon's entire culture was defined in mid-2022 by those who had fled from Twitter in early 2022, so it's based on Mastodon 3.x without "Hide with a warning".
Besides, the vast majority of Mastodon users don't even know that Mastodon has "Hide with a warning", much less what it does. Precious few even seem to know that Mastodon has filters in the first place. And next to nobody knows what the non-Mastodon Fediverse has, nor do they care, also because most Mastodon users don't even know that the Fediverse goes beyond Mastodon, Pixelfed and PeerTube.
In addition, while Hubzilla is all about empowering its users to self-moderate their stream, the "Mastodon experience" is generally perceived as being coddled and pampered all over. By mods who remove unwanted content and by all the other users who hide uncomfortable content. Hide it from everyone all the same, regardless of whether or not someone needs that, just because
one person
needs it.
So back to the beginning: This person took Mastodon's culture to the absolute extreme. And they demanded that I a) adopted Mastodon's way even though it'd b) clash with Hubzilla's culture which is my native culture and c) exaggerate it to the maximum.
Of course, my suggestion to use "Hide with a warning" filters didn't come to fruition. For one, that would have required an infinite number of individual filters on Mastodon. Besides, that person felt entitled to have protection from
literally absolutely any and all kinds of content
served to them on a silver platter.
I think I ended up Superblocking them.
#
Long
#
LongPost
#
CWLong
#
CWLongPost
#
FediMeta
#
FediverseMeta
#
CWFediMeta
#
CWFediverseMeta
#
Fediverse
#
Mastodon
#
Hubzilla
#
CharacterLimit
#
CharacterLimits
#
CharacterLimitMeta
#
CWCharacterLimitMeta
#
CW
#
CWs
#
CWMeta
#
ContentWarning
#
ContentWarnings
#
ContentWarningMeta
#
MastodonCulture
1
Link zur Quelle
Konversationsmerkmale
Lädt...
Lädt...
Konversationsmerkmale
Lädt...
Lädt...
Anmelden
E-Mail oder Kennung
Kennwort
Angaben speichern
Anmelden
Zurücksetzen des Kennworts
Entfernte Authentifizierung
Registrieren
