What should we do about Threads?
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 are viewing a single comment
I'm brand new to Lemmy (guess why, lol) and federated systems in general. How do I block all things Meta? And what does that even mean for Lemmy, where it's an entirely different site from Facebook?
As of now, there's no built-in means to block entire instances as a user. The only way to keep them out are to use an instance that is 2 levels separated from them, that is an instance that doesn't federate with another instance that federates with them.
Alright, that kind of answers the "how do I block Meta bullshit?" question, but what does that mean for Lemmy? Lemmy is an entirely different site from Facebook or Threads or whatever. Or is Lemmy more like a browser to view anyone's federated community? Then I'd get the EEE thing everyone's talking about. You usually see your communities on Site A, but Site B offers what Site A has, but also free beer! People migrate to Site B, Site B slowly introduces ads, poisons the beer, kills your cat, and steals your wife, but Site A is a shell of it's former self and dies out, so...you can't unfuck what's been fucked.
ActivityPub is the protocol that Lemmy/kbin/Mastodon use, and is the basis behind the fediverse. It's also the same protocol that Threads uses. They're all different site/services, but they can all interact with each other through the ActivityPub protocol, assuming they are federated to each other.
At the moment, Threads is entirely separate, as they haven't federated with anyone, but eventually they will want to join the fediverse, and the question is whether or not to federate with them. They will always be able to view our content as it's public, but if we federate with them we will see their content and they will be able to post content here. Keep in mind that Lemmy currently has about 70k active users, and that Threads just got 30 million+ sign-ups. We don't know how many of those are active users, but it's certainly more than all of Lemmy put together. If they come here, that's going to be basically impossible to moderate.
Ahh, so if I'm on Site A, I can view and comment on things from Site B, so long as A and B are federated with one another. The worry then is basically seeing and dealing with Meta's bullshit here, and them more or less taking over through EEE tactics. That makes sense now.
Lemmy communities aren't federated with Meta threads by default, right? It's opt in. So just...don't federate with .meta or whatever they'll use? Apart from "don't affiliate with The Zuckerbot", I'm still not sure what the worry is all about.
There's a bit more to it, but essentially yes. For example, beehaw.org has defederated from lemmy.world, but we can still view their content. We can interact with their content and reply to their posts, and other instances that they are federated with can see what we do there, but beehaw users can't see any of it. Basically federation is a one-way street. You can federate with an instance, but they don't have to federate back.
That's kind of the motto of the fediverse in general. It's supposed to be de-centralized and de-corporatized. There are no built-in features for advertising, for example. It's meant to be a place that is safe from the things that we're afraid Facebook is trying to do. Overall, it mostly is. They can attract people out of the fediverse and into their garden which they plan to wall off, but they can't quite shut down the independant instances.
Ahhh, now it makes sense, thank you! So...do we panic because Zillaberg is making a federated Twitter sequel, or...?