#ContentWarningMeta

Tufty Indigo 🪗Proposal to make Mastodon's content warnings work like the Met Office's weather warnings, as explained by the BBC:-<a href="https://meow.social/tags/ContentWarningMeta" class="mention hashtag" rel="nofollow noopener" target="_blank">#ContentWarningMeta</a> <a href="https://meow.social/tags/humour" class="mention hashtag" rel="nofollow noopener" target="_blank">#humour</a>

Jupiter Rowland@<a href="https://social.wedistribute.org/users/damon" rel="nofollow noopener" target="_blank">damon</a> It doesn't help that Mastodon itself is largely a bubble. Some 70% of all Fediverse users are on Mastodon. But it seems like that within Mastodon itself, at least 95% of all posts originate from Mastodon. Maybe even more. There are several reasons for this. First of all, other projects don't federate with Mastodon that much. Misskey is huge in East Asia, especially Japan. And Japanese Misskey users who hardly know English or not at all won't be interested in connecting with Western Mastodon users, so a large chunk of the second-biggest free project in the Fediverse is out of the equation. Lemmy is the third-biggest, but Lemmy federates with Mastodon only barely so, also because Lemmy is all about discussion groups and enclosed conversations, both of which Mastodon simply doesn't support. Lemmy users can't follow Mastodon users because Lemmy users can't follow users, full stop. And Mastodon users have to wrap their minds around how to federate with Lemmy. It isn't as straight-forward as communication within Mastodon. And so they simply don't. Other examples include Hubzilla and (streams) channels having ActivityPub off on purpose to keep ignorant and obnoxious Mastodon users out. But this goes the other way as well. Mastodon can be outright hostile to non-Mastodon users. Why? Because they don't behave like what Mastodon users are used to from Mastodon and, by extent, partly also Twitter. And they have joined the Fediverse in expectation of something that's one big distributed but homogenous Twitter clone. Anything that deviates from that may be disturbing. There are Mastodon users who, upon seeing a post with over 500 characters, and be it in the federated timeline, block the poster. This alone cuts into the reach of everything that isn't Mastodon. Not few wish for a switch with which they can permanently filter out all posts with over 500 characters. Others may block everyone who uses text formatting. Either it simply goes on their nerves. Or they can't imagine that it's even possible to format text in the Fediverse because they can't do that on Mastodon, so they think it's all some Unicode trickery. And as this Unicode trickery is not accessible and inclusive because it irritates screen readers, they deem whoever uses text formatting ableist and therefore blockworthy. Then there's the issue of content warnings. They must be provided the Mastodon way, or you risk being blocked. However, not everything out there provides a) the right text field with b) the right label on it. Non-Mastodon projects may still label the summary field a summary field instead of a CW field like Mastodon does. Friendica, for example, has done away with that text field entirely and users BBcode tags instead. Hubzilla doesn't provide any means of adding a summary/a Mastodon CW to a reply. And both have had their own way of adding CWs since long before there was Mastodon which their own users consider vastly superior to Mastodon's way. In general, boosts are very important on Mastodon. I'd say that most activity on Mastodon is boosts because they're so easy to do on a phone without a hardware keyboard. Your reach on Mastodon depends on boosts. But if you don't play exactly along Mastodon's written and unwritten rules, and if you don't adhere to the "Fediquette" which is entirely defined by only Mastodon users and geared towards only Mastodon's features (or lack thereof), you're boosted far less. If you post more than 500 characters at once, it takes a lot for your post to get boosted. If you post an image without alt-text, the post will be boosted dramatically less because not exactly few Mastodon users refuse to boost image posts without alt-text. You may even be muted or blocked for not providing alt-text. But alt-text only is a thing on Mastodon, and hardly anyone provides it outside Mastodon. In general, anything that deviates from the standards defined by vanilla Mastodon will cut into your visibility on Mastodon deeply. CC: @<a href="https://social.fedcast.ch/users/Hiker" rel="nofollow noopener" target="_blank">Hiker</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediquette" rel="nofollow noopener" target="_blank">Fediquette</a>

Jupiter RowlandMy most recent introduction post as per August 7th, 2024; CW: long (xx,xxx characters), Fediverse meta, Fediverse beyond Mastodon meta, alt-text meta, image description meta, content warning meta, hashtag meta

Jupiter Rowland@<a href="https://mastodon.uno/@talksina" rel="nofollow noopener" target="_blank">Elena Brescacin</a> @<a href="https://eldritch.cafe/@Lucia" rel="nofollow noopener" target="_blank">:sigil:🦇Luzífer🦇:sigil:</a> You must consider that not everyone is on Mastodon, that not everything else in the Fediverse is like Mastodon, and especially, that not everything else in the Fediverse has a text field labelled, "CW" or "Content Warning". Really not. (1/10) #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseIsNotMastodon" rel="nofollow noopener" target="_blank">FediverseIsNotMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonIsNotTheFediverse" rel="nofollow noopener" target="_blank">MastodonIsNotTheFediverse</a>

Jupiter Rowland@<a href="https://graz.social/@publicvoit" rel="nofollow noopener" target="_blank">Karl Voit :emacs: :orgmode:</a> Der Abschnitt "Update: Friendica posts in Mastodon" ist nicht nur sachlich falsch, sondern auch noch stark unvollständig. Ich als langjähriger Hubzilla-Nutzer mit Friendica-Vergangenheit würde das eher so formulieren: Update: Posts and comments from Friendica, Hubzilla and (streams) in Mastodon Posts and comments coming into Mastodon from Friendica, Hubzilla and (streams) are special cases. That's because neither of them have Mastodon's dedicated CW field. Instead, they have reader-side content warnings that can optionally be created automatically. By default, a post is automatically hidden behind a content warning button if it contains "nsfw" and/or "sensitive". Automatic reader-side content warnings have been part of the culture of both Friendica and Hubzilla since before Mastodon was even made as well as of fairly new (streams). Poster-side content warnings in a dedicated field have never been part of their culture, both because they've got a much better solution for content warnings and because they don't provide dedicated means for poster-side content warnings. Technically speaking, Hubzilla and (streams) do have Mastodon's CW field. But unlike Mastodon, it isn't labelled "CW". It's labelled "summary". It has been a summary field originally, but since a hard-coded maximum of 500 characters doesn't require summaries, Mastodon repurposed that field for content warnings. Hubzilla and (streams) have no character limits at all, so using that field for summaries is still justified. Hence, Hubzilla and (streams) users use this field for short summaries for very long posts, if at all, but not for content warnings. Also, just like Friendica, both Hubzilla and (streams) have a conversation model like Facebook or Tumblr or blogs with only one post and many comments. All replies are comments, and there is a separate, dedicated entry form for comments under each post. This entry form does not, however, have a summary field because what sense does it make to give a summary for a blog comment? Hence, Hubzilla and (streams) users can't put Mastodon-style content warnings on replies at all. Also, neither Hubzilla nor (streams) can re-use content warnings from posts or comments they reply to. Friendica, the oldest one of the three, doesn't even have a dedicated summary field. The only way to add a summary, i.e. a Mastodon-style CW, is between the Friendica-specific BBcode tag pair <code>[abstract][/abstract]</code>. This works in both posts and comments, but the availability of this tag pair is neither advertised in the post editor nor in the comment editor. Since Friendica doesn't have a dedicated UI element for Mastodon-style CWs, neither for posts nor for comments, most Friendica users don't give Mastodon-style CWs at all because they simply don't know that this is possible in the first place, much less how. Also, users of Friendica, Hubzilla and (streams) tend to find the idea of writing a content warning between a pair of obscure BBcode tags (Friendica) or into the summary field (Hubzilla, (streams)) ridiculous. Trying to convince them otherwise would be like trying to convince Mastodon users to double their CWs with keywords or hashtags to trigger the NSFW content-warning generation on non-Mastodon projects. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener" target="_blank">(streams)</a>

viqI'm finding I'm using <a href="https://social.hackerspace.pl/tags/ContentWarning" class="mention hashtag" rel="nofollow noopener" target="_blank">#ContentWarning</a> in situations where I'm not sure I'm reading the situation right, and I'm not sure the person would be interested in seeing my long form comment. Somewhat "here's a short description of what I write about, if you're interested click to open, if not that's fine too" 🤔 <a href="https://social.hackerspace.pl/tags/ContentWarnings" class="mention hashtag" rel="nofollow noopener" target="_blank">#ContentWarnings</a> <a href="https://social.hackerspace.pl/tags/CW" class="mention hashtag" rel="nofollow noopener" target="_blank">#CW</a> <a href="https://social.hackerspace.pl/tags/ContentWarningMeta" class="mention hashtag" rel="nofollow noopener" target="_blank">#ContentWarningMeta</a>

Recent searches

Search options

Administered by:

Server stats:

#contentwarningmeta