#cwblocklistmeta — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #cwblocklistmeta, aggregated by home.social.
-
@Kevin Karhan :verified: To quote Arthur C. Clarke:Any sufficiently advanced technology is indistinguishable from magic.
And for your average Musk escapees, Mastodon alone is more than sufficiently advanced. These people believe that there's some magic going on that makes their fully public posts private and secure regardless. They want perfect security, but with zero inconvenience, and they think Mastodon provides them with exactly this.
In fact, they expect Mastodon to be an absolutely perfectly safe haven, simply because it isn't a corporate silo. Little do they know how close to being a corporate silo Mastodon is, what with having a US-based company and a lighthouse instance that accounts for 22% of the whole Fediverse in terms of MAUs.
On top of that, more than half of all Mastodon users think the Fediverse is only Mastodon, and most of the rest can't imagine that anything in the Fediverse could possibly have features that Mastodon doesn't have. Not unless you slap them right into their faces like character limits over 500.
They cling hard to and rely on an imagination of the Fediverse that has never even been close to reality and never will.
As for The Bad Space, its blocklist looks like it's curated not by evidence, but by emotional triggers. Generally, some blocklists go so wild that you have to ask yourself whether the reason why nobody has tried to block out everything that isn't vanilla Mastodon is because that'd be too big an effort (two out of three Fediverse instances aren't Mastodon), or whether such people simply don't know how far the Fediverse extends beyond Mastodon, so they don't know what to block. I mean, there should be reasons enough to block everything that isn't Mastodon.
Blocklist import from other instances doesn't make things any better. Just like on all networks where everyone can run a server, the Fediverse, especially Mastodon, has got admins who really shouldn't run a server. It looks very tempting to pick blocklists by length rather than content, the longer, the more "secure", import a bunch of them, but not curate them because that'd be extra effort.
In this light, it's a good thing that Oliphant put the tier-1 to tier-3 blocklists onto the chopping block when switching from manual list curation to automated list aggregation a while ago. Especially tier 3 would have been easy to exploit with little to no curation, and there certainly were enough sufficiently paranoid Mastodon admins who'd subscribe to tier 3 without ever taking a single peek at the list.
Sometimes I feel like going to Mastodon's GitHub repository and submitting blocking or allowing entire Fediverse server applications by user agent, both for admins and for users, as a feature request, just to see what'll happen. Maybe dumbed down on the user side to a switch that blocks everything that isn't Mastodon. But maybe I should also mention that (streams) already has this feature on the admin side so that the Mastodon devs have to think up a way to sell this as invented by Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta -
CW: Only the two biggest Hubzilla hubs are on Threads' blocklist? CW: long (almost 1,200 characters), Fediverse meta, non-Mastodon Fediverse meta, Threads, blocklist meta
In case you haven't read it, maybe because it has only been circling in the ActivityPub-only parts of the Fediverse: Threads has published a constantly changing list of blocked Fediverse servers.
I'm actually genuinely surprised to only see two Hubzilla hubs on the list, hub.netzgemeinde.eu and hub.hubzilla.de, the two biggest ones. Curiously, unlike hub.netzgemeinde.eu, hub.hubzilla.de is not on the list for having has its pubstream off, and it does have its pubstream off.
Is it because Threads hasn't noticed the other hubs yet? Or is it because Threads ignores all instances with fewer than 1000 or 500 users in order not to clutter their blocklist too much?
I'm wondering because there may be more than one reason inherent to Hubzilla that's enough for Threads to block a hub. So in theory, all hubs should be on the list, maybe except for a few compliant private ones that can afford to have their pubstreams publicly visible. If there's a way for Hubzilla to fully comply with Threads' rules, that is.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Threads #ThreadsNet #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta #Hubzilla