floss.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
For people who care about, support, and build Free, Libre, and Open Source Software (FLOSS).

Administered by:

Server stats:

689
active users

#Decentralisation does NOT mean the whole #Fediverse should block #threads. Decentralisation means that every instance (and user) decides for themselves with whom to exchange communication. While this might look like chaos and a non-deterministic way of sharing information, it reflects the true nature of decentralisation. If you think it should be a binary decision of The Fediverse to not talk to Threads, you are still in the centralised mindset ...

Jiří Eischmann :fedora:

@jwildeboer what do you think of instances that block other instances just because they don't block Threads? That seems like the point where the Fediverse really disintegrates.

@sesivany @jwildeboer seems like a cultural problem to me. You could think that the Fediverse celebrates diversity, but a lot of folk seem to want to have it their way on every instance. So they apply political pressure to either achieve what they want, or to be otherwise satisfied from feeling important.

P.S. Not that I have been asked, now that I think about it.

@sesivany @jwildeboer They do what they want, but it will be impractical and impossible in practice. They’ll be completely isolated in no time. At this point, better just deactivate federation and abandon decentralization, just be your own little forum without activitypub.

You can’t even do IRC-style federation if you want to enforce complete separation with Meta. Whitelisting is no good either. There will be a path, one way or another that jumps from server to server will reach Meta.

The actual real solution is just to enable authorized fetch, and block threads.net. Nothing else works.