I honestly don’t know what my mastodon instance’s take on blocking threads is but I probably will be blocking them on the account level. Blocking servers transitively because they don’t defederate with meta seems like it is unnecessarily siloing servers into a second “free” fediverse. If a server is moderating their accounts in accordance to the written policy then if they choose to federate with meta, it doesn’t feel like it’s any of my business.
Fediverse
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
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.