Instances in the free fediverses should consider "transitive defederation" from instances that federate with Meta (privacy.thenexus.today)

submitted 10 months ago by thenexusofprivacy@lemmy.blahaj.zone to c/fediverse@lemmy.world

142 comments fedilink hide all child comments

cross-posted from: https://lemmy.blahaj.zone/post/7477620

Transitive defederation -- defederating from instances that federate with Threads as well as defederating from Threads -- isn't likely to be an all-or-nothing thing in the free fediverses. Tradeoffs are different for different people and instances. This is one of the strengths of the fediverse, so however much transitive defederation there winds up being, I see it as overall as a positive thing -- although also messy and complicated.

The recommendation here is for instances to consider #TransitiveDefederation: discuss, and decide what to do. I've also got some thoughts on how to have the discussion -- and the strategic aspects.

(Part 7 of Strategies for the free fediverses )

you are viewing a single comment's thread
view the rest of the comments

[-] ____@infosec.pub 4 points 10 months ago

While my primary masto is a single user instance, basically anywhere else I exist on the fedi is a subset of infosec dot *.

Those instances are all run by someone who a) is cool with spinning up a whole bunch of instances, b) is willing to risk the costs, and c) is excellent at delineating policy. There’s a “no fucking threads full stop” instance, and a “no threads by default, but user can flip switch” instance, for example.

That’s a method of operation that works from my pov but doesn’t suit everyone’s needs. Personally, I want nothing to do with threads but am more able to express my anti corp tendencies than I was in my twenties, and I’m more willing to accept that “it’s just bandwidth, find the instance that meets your needs.”

My needs involve no threads at all, but I can accomplish that with a very small amount of effort given. My circles.