A lot of people dislike it for the privacy nightmare that it is and feel the threat of an EEE attack. This will also probably not be the last time that a big corporation will insert itself in the Fediverse.
However, people also say that it will help get ActivityPub and the Fediverse go more mainstream and say that corporations don’t have that much influence on the Fediverse since people are in control of their own servers.
What a lot of posts have in common is that they want some kind of action to be taken, whether it’d be mass defederating from Threads, or accept them in some way that does not harm the Fediverse as much.
What actions can we take to deal with Threads?
You must log in or register to comment.
Some food for thought from Mastodon:
https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/
Join the pact and not just vow but actually do defederate Threads as soon as it comes online: https://fedipact.online/
Here’s Eugen Rotchko’s thoughts.
https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/
What an excellent article. Informative and to the point.
Recommend everyone read it.
It’s a clear EEE attack. Do not federate!
This makes zero sense. There is no financial incentive for an EEE attack, and these companies don’t do anything without financial incentive.
Your content isn’t original or interesting enough for meta to want it, and even if they did, they already have access to it without federation.
Threads on its own already dwarfs the entirety of the global fediverse by orders of magnitude. Anyone screaming EEE is just fucking stupid.
I think we should defederate any corp version of any federated app. Not due to privacy or anything, but because it silos anyone using those services from everyone else. Bluntly, I don’t want people’s B.S. propeganda on the fediverse, and the stupid crap conspiracy farm that Facebook and other places have become.
I’m sure it won’t stop the stupid from reaching us, but it should limit the amount and impact that those users have. Additionally, it will remove a lot of high quality content from those services making them less viable for corps to run and maintain. They will happily farm the fediverse for content to attract users they can monitize… I’m not a fan of handing them more content to steal while they share zero of the profits of that content with either the creators or the communities that handle that data.
I’m not doing their job for them in promoting entertaining and informative posts just so they can make money on it. They want it, they can put forth the effort themselves.
Put another way, given the size of Meta and its userbase, it’s completely infeasible for a typical instance to moderate on their behalf, so defederating due to insufficient moderation makes sense. Just like with Beehaw and sh.itjust.works or whatever. (I take for granted that moderation will suck ass because gestures vaguely at Facebook.)
That’s a good enough reason for me. I also think federating with Meta is a bad idea on principle and out of self-interest, since they will extinguish the fediverse at the first possible opportunity and federating with them gives them the chance to draw in users and later wall them off.
The EEE argument is a red herring at the moment. Sure, in the future, Meta and others could get clever in ways we can’t imagine right now, but currently it’s a “sky is falling” kind of threat. As it currently stands, the path from Threads launching to “Meta killing the fediverse” has all the logical progression as the Underpants Gnomes.
You’re right. It’s all FUD at this point. There’s nothing stopping servers from federating for now and then disconnecting later if an actual issue comes up.
The problem is like the boiling frog analogy. Its never easy to get consensus on whether the latest insult is too much and so inertia holds everyone in place until its too late.
Make an account and use chatgpt to shit post on it.
threads will never federate.
