I really want to nip threads in the bud. Besides blocking threads.net itself, defederate from any instances that do not. This is blatantly an EEE strategy and a united front is the only way to save what have been accomplished. Here is how Indivudals can do it on mastodont as an example to follow. https://hachyderm.io/@crowgirl/110663465238573628 Edit found this , https://fedipact.online/ please sign.
The fediverse wasn’t irrelevant yesterday and it won’t be if it defederates Meta proactively before they have the opportunity to ruin the ecosystem.
If you defederate with non-meta instances you’re going to vastly reduce local content and encourage people to give up and go somewhere else. What good would that do? Like I said I’m for defederating with Threads, but attacking everyone that doesn’t is a waste of effort and is going to ruin the community.
Due to the architecture of the fediverse instances federated with Meta give them access to the data of those on those instances, even if they’re not meta owned. Defederate on is afaik the only way to stem that flow.
That’s not the danger. It’s super easy to gather data on the Fediverse, I can just self-host an instance and connect with everyone and scrape the internet and all that.
The danger, from my pov, is that people would be so dependent on major companies that they can hold a power position over the Fediverse. If 90% of people on your instance use Threads, and Threads decides to defederate or slowly creep in proprietary features you’re not allowed to use, people would feel like they’re being forced to make an account there or leave smaller instances. That’s the EEE scenario, I don’t think privacy (from our end) is a huge concern right now.