- cross-posted to:
- technology@beehaw.org
- fediverse@lemmy.world
- cross-posted to:
- technology@beehaw.org
- fediverse@lemmy.world
Server indexes of places for newcomers to join can be instrumental for Fediverse adoption. However, sudden rule changes can leave some admins feeling pressure to change policies in order to remain listed.
I’m kinda against defederation or blocking anything at an instance level, unless the instance causes straight up legal issues or is literally created for the sole purpose of harassment
Well, I think Threads meets your litmus test requirements.
It is a certainty that Threads will heavily influence the future development of Activity Pub. This will inevitibly lead to the corporatization and enshittification of any service Threads can affect.
The only resistance we can offer against this is defederation and noncompliance with the will of the behemoth.
You’re missing the point. Fedi Garden is threatening to defederate from anyone who doesn’t defederate from Threads.
Imagine if other instances start doing this about things that aren’t threads. “Delist from db0 or world will delist you”, “delist from Lemmy.ca or Lemmy.ml will delist you.”
I understand your “what if” scenarios, but this is an existential crisis that needs to be resisted against with all instances working in concert. This is not a “what if” scenario. This is the actual iceberg and it is big enough to ruin the fediverse for all instances, no matter their affiliation with the garden.
So, we either unite to defend the independence of the fediverse, or we let a corporate giant take it by ovewhelming us with their “important updates for your security” until we are all assimilated.
Ngl, this screams “think of the children.”
When they have a track record like this?