If we're going to have an effective strategy against FB/Meta, we should clear up some misconceptions around defederation
((I'm not an expert, I've been reading up on things as much as I can. If there's an error, I'll happily correct it!))
TLDR:
Nearly all of us distrust Meta and have the same broader goals
We need to pick the best move to go against powerful companies like Meta
Defederation may not be the right move, and it might even help Meta move forward (and more easily perform EEE)
There are other options that we can spend our energy on
It doesn't matter for Lemmy (yet), this is more a conversation for Mastodon, Firefish and Kbin
We've been getting a LOT of posts on this, but the misconceptions make it harder for us to decide what to do. If we're going to try and protect the Fediverse against large, well funded companies like Meta, figuring out the right action is important. We need to actually look at the options, consider the realistic outcomes, and plan around that.
I'm willing to bet around 95% of users on Lemmy and Mastodon CHOSE to be here because we understand the threat Meta/Facebook poses, and we want to do something about it. That's not in question here.
So in that sense, please be kind to the other user you are replying to. The vast majority of us share the same goal here. When we disagree, we disagree on the best path forward and not the goal. Wanting to stay federated DOES NOT mean the user wants to help Meta or thinks that Meta is here for our benefit.
Misconception: Defederation will hinder Meta's EEE
It might, but not necessarily, and it might even help the EEE. Here's a link to some history of EEE, what it means, and some examples: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish. I'd recommend at least skimming it because it's interesting (and because this isn't the only fight)
Assuming Meta is doing an EEE move, they're in the embrace stage. That’s not about us embracing them, it’s about them embracing the protocol, which they can do whether we stay federated or not.
Defederation can tell newcomers that the defederated instance is an island, and they’re better off joining the place where they can talk to their friends and see the content they want. We saw this early during the Reddit exodus with Beehaw, where many users hopped instances away from Beehaw.
Meta can more easily embrace if more people actively use their platform. They can more easily extend if we're not around to explain why extending is a poisonous action. Being federated can allow us to encourage users to ditch Meta’s platform and join an open one (ex. Mastodon, Firefish, etc.)
Misconception: Defederation is the only move
Defederation is the first option that comes to mind. It sounds simple, it is loud and newsworthy, and it can be done with the click of a mouse. But if it is a bad action, then what are the good actions?
Don't let them have a monopoly over the use of ActivityPub. Grow the other platforms: The extend stage only works when the platform gets a near monopoly over use of the standard. That brings up the first action. If there are enough users, services and resources on things like Mastodon/Lemmy, then Meta (or any other company) can't just extend the spec without causing their users to ditch Threads to stay connected to the content they want to see.
Reach out to organizations in your area or line of work. Help them join Mastodon or other relevant Fediverse platforms. I'm sure the for-profit companies put money into this process, so brainstorm and reach out
Add your Fediverse accounts to the bio of your other accounts, and share posts from the Fediverse elsewhere
As long as there is a healthy community away from Meta (ex. what we have right now), then they can't extend & extinguish.
Protect the Standards and share why it is important
Share posts from experts about strict adherence to standards, support regulatory and legal advocacy (interoperability requirements etc.), and educate other users about the risks.
(I didn't want to say more here because I'm not an expert, I'm happy to edit more points in)
Misconception: We should still defederate because of Privacy Risks
Not necessarily (and likely not at all?)
Meta is notorious for gathering data and then abusing that data, so this is an issue to consider. However, the way that activitypub works, the outgoing data is publicly available. Defederating with Meta doesn't prevent that, and federating doesn't give them any more data than they could get otherwise.
Misconception: Lemmy instances need to decide
This is a big point: It doesn't really matter for Lemmy right now, one way or another.
It's more of an issue when data starts coming IN to Lemmy from Mastodon and Meta's Threads (or out from Lemmy to Threads). See below
Edit to add: For now it might even be good to defederate from Lemmy as a symbolic gesture. My instance is defederated, and I don't plan on trying to change that. Ultimately it doesn't change much
Legitimate risks from Federation with Meta, and more effective ways to counter them
Algorithmic Amplification: Meta's history of using algorithms that prioritize engagement can amplify harmful or divisive content. These algorithms are not public like it is with Mastodon and other FOSS platforms.
Misinformation and Content Moderation: All Fediverse platforms will have to work on content moderation and misinformation. Platforms like Meta, focussed on profit and advertising, will likely moderate in a way that protects their income. Those moderation decisions will be federated around.
Commercialization and User Exploitation: Meta's for-profit nature means it's incentivized to maximize user engagement, at the expense of our well-being.
Additional Data on how the free fediverse interacts with their platform (this one is harder to make a counter for)
Counters:
Promote user control over their feeds, and develop USEFUL but safe and open algorithms for the feeds
Flag content and users from risky platforms, with a little warning icon and explanation (ex. 'Content is from a for-profit platform, and it may ___')
Implement features so that users can opt in or opt out from seeing content from risky platforms. In particular on explore/discover/public feeds, so it doesn't affect content the user is following.
Develop strict community guidelines that can get Meta (and other companies) sent into the 'blocked by default' bins mentioned above. (edit: There's a good point here that if Meta'a Threads is full of hatred or poor moderation, then blocking them is the right move)
Final point: Evaluate things critically. Don't even just take my word for it. I doubt Meta or other groups care enough about Lemmy yet to spread disinformation here, and every post I've seen promoting defederation feels like a good faith attempt for something they believe in. But it's still worth thinking about what we're supporting.
Sometimes what feels like a good move might not help, and could even make things worse.
This entire argument is bullshit. Meta needs to be an island from our perspective. Let them do their thing over there, we'll do our thing over here. Their goal is to lure (probably former reddit or twitter) users to Threads and then cut off the greater Fediverse as a whole once their user base is established and much larger than ours. And they want to use our numbers to boost their for profit platform to make it appear more successful.
Separation from these kinds of corporate entities is exactly what the Fediverse is about. We can talk about "open" all we like but there is already a short list of bad actors we don't allow here: Nazis and fascists, pedos and kiddie diddlers, etc. We can add Meta to that list as well.
We don't want them interacting with us at all. Get out the hammer and ban them. Entirely.
I'll add an edit to say this: I say that defederation is not extreme enough. They need to be blocked. Instances need to implement ToS and licensing that prohibits them from hoovering up and regurgitating our content. We need to start outright blocking Meta at the network level. Whatever the hell it takes. Line in the sand. No means no.
No Meta. Ever.
Think of this: In the past, we have never had any choice other than to roll over and accept whatever bullshit the major social media companies push on us. If you want to communicate, if you want to use any platform, if you want to be in, you had to deal with them and their system. Because they were big and you were little, and what are you going to do about it? You have no choice but to roll over.
Well, we don't have to roll over anymore. We have this one -- and believe me, only this one -- opportunity to unequivocally tell them NO. We are not your product. You have no value to us. You aren't a monopoly anymore. We do not need your corporate influence, we do not need your corporate bullshit. We are free of you, and we don't need you.
Another edit: Oh, look. What do I find right at the top of my feed first thing this morning? Why, it's yet another example of Meta being evil. And you still want them to have influence in the Fediverse?
I fully agree that it doesn't matter for Lemmy right now. The issue is mostly Mastodon and Kbin, as both compete directly with Threads; and in a smaller scale Friendica, Matrix and PixelFed as they compete with FB/WhatsApp/IG.
The main reason why I support defederation is to not have users in Mastodon relying on contacts and content from Threads at all. Because, once Threads pulls off the plug (eventually they will want to), Mastodon won't be some small but stable network; it'll be a shrinking one, and that's way worse.
mastodon implements it, pleroma/akkoma probably implements it, pixelfed implements it, firefish and iceshrimp implement it (sharkey has a PR implementing it opened just today), gotosocial not only implements it but enforces it, with no ability to turn it off
notably, none of the threadiverse software implement it, and no software other than the aforementioned gotosocial enable it by default.
I think we should encourage politicians, governments and public figures to either self host or use non-threads instances. That way, Threads cannot easily shut off AP support or screw around too badly or their own content will decline.
Right now, social.bbc is a thing. Hopefully when threads launches activitypub, they'd notice that having a presence on both threads and their own instance is pointless, and prefer their own instance
Im pretty sure meta give zero fucks about joining the fediverse beyond trying to destroy it. I imagine they only started threads to nullify it by either proving it doesnt work (threads looks pretty garbage) or they want to control the content where mainstream fediverse will never take off.
Im here because i liked reddit but hated being a product. Meta/facebook was zero percent of that initial switch calculation as i havent been on their stuff for nearly a decade. The api shutdown ay the alien site was the last straw. I dont want to interact or give data to facebook/meta. Just my two cents.
I want to throw this into the mix, but something that kept getting ignored early on during the reddit departure was the implications of defederation on how that effects networked systems.
It's part of the math of social graphs, but bad faith instances and teolling, severely impacted Lemmy's initial ability to catch on. By defederaring you massively reduced the total size of the network interactions that take place ( even if it's very important to do so ).
This has the potential to allow meta controlled instances to rapidly out populate non meta controlled instances. From there it's only a matter of time before they end up with a seat on the activity hub team. Then we're back where we started.
I'm ok with instances defederating because it gives them time to wait and see how to handle the influx and what other unknowns might happen, but I agree that it's just not a strategy to stop EEE. We need to do more and do it smartly.
To me it's like a trade war, we have a couple strategies we can do. Isolationism is one of few options that I can think of that has only failed historically. I'm ok with protectionism even better when it's just reusable user protections, like automating ad blocks, sponsored content blocks/labels, etc, but also maybe we do things like not federation communities from Threads, definitely blocking anything that isn't in the open spec.
I like your take. Unfortunately, I don’t see a way forward where Meta isn’t at least partially successful in extinguishing the fediverse. We’ll probably be fine, because we’re here now and our shit works, but the most likely scenario I see is in the future the common perception of fediverse microblogging apps will be, “oh, that place where users can never see when I’m using ___ feature.” Then it will be harder to attract new users, just like it was so hard for Firefox to attract users when sites were broken because of IE’s EEE tactics.
I’m mostly afraid of spam. I don’t mind if a company wants to advertise to their own user base, but I definitely don’t want to deal with spam from elsewhere. I hope the protocol addresses this in a way.
I’d like to see the fediverse embrace and extend, rather than meta.
Money is going to be involved at some point, better make the rules now before meta does.
AFAIK, Meta cannot modify algorithms in lemmy code / created in networks inside lemmy instances (if that’s s thing) unless meta starts running those instances themselves. No doubt, using meta’s instance and client will let meta do what it wants to do.
I think the harder problem here is meta isn’t a curated collection of 300+ instances we can block when we don’t like the instance (e.g., instances != facebook communities). Meta is just going to come online with a large instance with millions of users. It’s kind of hard to judge all of meta users at once, as an instance provider. So, I guess instances who don’t want meta, don’t get meta. Fair.
I agree with all the misconceptions you’ve cleared up, and you’ve also made a great case for why people would want to join a smaller private instance instead of facebook. I guess I just don’t see the present threat to the fediverse with meta (aside from instances being bombarded with trash that needs to be defederated from that instance). There’s absolutely an existential threat, but the beauty of open source is that as long as there are devs willing to work on it, it can still exist - meta cannot buy the current version of lemmy we are all using and prevent it from being run, for example.
I'm pretty sur meta doesn't care to federate. I bet they will even defederate rather aggressively to enforce their moderation.
IMO federating is a good move to steal users from it. There is no user to steal for meta, people here are here because they fled the other platforms. Meta users though are unaware of this other world, and they can easily be brought in if they can discover it.
I'm sorry but your post just doesn't make sense for me.
It's well written, and there are a lot of good things "everyone" should do, but they are a one man with a 1.000 times us army. We twiddling here and there will just make it easier to do whatever they want.
We need a clear idea and way forward.
Or several, because that will battle harden those ideas, and we'll see which new idea we should follow.
I know you put lot of effort into this post, but I'm sure as hell going to defederate with meta, microsoft, and actually even an eventual enormous Lemmy instance if it's using predatory algorithms.
I'm here to share my knowledge and learn from people who are interested in the same things as I am, see some new stuff, love live laugh a bit with memes. I'm not here to waste my life or generate revenue.
I'm not sure it's as big of a deal with Lemmy. Threads data doesn't map very well into Lemmy and vice versa. Like with Mastodon, I can read this post and comment on it, but it's not really a great way to interact. I think it's a bigger deal on the Mastodon/Calckey/etc side. If IG/FB federate then it becomes a different story, IMO.