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
Artikel ansehen
Zusammenfassung ansehen
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
