If Mastodon's various user interfaces won't constantly advertise groups after Mastodon has introduced them, nobody will use them; CW: long (almost 1,800 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
Artikel ansehen
Zusammenfassung ansehen
When Mastodon introduces groups, it had better also introduce a strikingly big "Groups" button to its Web interface and the official iOS and Android apps. And the major third-party phone apps had better follow suit as soon as possible.
Otherwise the majority of Mastodon users won't even know that the Fediverse has groups (it does right now, and they don't right now), much less that Mastodon has introduced them. And they'll go on shouting into the void like they've always done, hoping that the right people may happen upon their posts.
I mean, Mastodon has also copied Friendica's, Hubzilla's and (streams)' automatic, reader-side content warning generation into its existing filters and rolled that feature out with Mastodon 3.0 in October, 2022.
But next to nobody on Mastodon even knows that this feature exists
anywhere in the Fediverse, much less on Mastodon itself. For the huge majority, putting content warnings into the summary field (of which next to nobody on Mastodon knows that it's actually a summary field) and forcing the very same content warnings on everyone in the Fediverse is without an alternative. As is demanding that the very same content warnings that one requires oneself be forced upon everyone else while oneself be spared from all other content warnings.
And, in fact, it also seems like hardly anyone on Mastodon knows that you can follow hashtags on Mastodon, just like you can follow people. There's no big honking button in front of everyone's noses for that either.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Friendica #
Hubzilla #
Streams #
(streams) #
Groups #
FediGroups #
FediverseGroups #
CW #
CWs #
CWMeta #
ContentWarning #
ContentWarnings #
ContentWarningMeta
