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?
we shouldn’t do anything.
Isn’t the whole promise of the fediverse that whatever the policies of one instance are, that doesn’t necessarily affect all the other instances, and each can do their own thing. If an instance doesn’t want to accept traffic from threads, good for them. But to try to organize a fediverse-wide response to threads seems a whole lot like the centralization the fediverse is supposed to not be.
Agree, by design the fediverse should be able to resist whatever the supposed harm is from META, I don’t really agree with privacy concerns since everything on the fediverse is public, especially on kbin and lemmy, almost everything is already available to whomever eants it, there is no need to set up this hugr machination since they can already accomplish it so much easier.
Well the resistance isn’t without reason:
https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
I’d like to add to this that there’s no particular benefit to defederating preemptively instead of defederating in response to a problem.
Also, is this a problem we need to deal with? I think it matters for Mastodon instances, but I don’t think Threads users will be interacting with Lemmy.