342
Lemmy.ml has now blocked threads.net / Meta
(lemmy.ml)
It should come as no surprise that the lemmy.ml admin team took about 2 minutes to decide to pre-emptively block threats / Meta. Their transparent and opportunistic scheme to commodify the fediverse and it's users will not be allowed to proceed.
We strongly encourage other instance administrators to do the same, given the grave threat they pose to the fediverse.
https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish
Embrace: they embrace the fediverse, bring millions of new users to it and everyone is happy. The fediverse grows and the new meta instance gets a ton of content. Everyone is happy
Extend: meta begins to add features to their instance which clashes with or is unusable with other instances. These begin to pile up and issues develop.
Extinguish: meta unfederates from other instances. People are now forced to stay where they were and lose a majority of their friends and content from metas instance. Or switch over. Mass migration away from original instances. These instances die
https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
How is that different from defederating now?
In the Embrace, Extend, Extinguish scenario, assuming they get to "Extinguish", the rest of the Fediverse becomes isolated and cannot connect with their friends and content.
If we defederate now, the Fediverse becomes isolated and cannot connect with Threads content, and cannot connect with friends who choose to be on Threads instead of a disconnected alternative.
expired
The difference is time. With time a federated Threads will build it's own massive library of content, suck in it's own users and then slowly make all of that proprietary and locked down from the rest of the fediverse.
It's a long con that's been done several times by big corporations.
De federate now and that content and those users will have to choose now. Meta or fediverse. The scales are still uneven, but less uneven than in that future.