this post was submitted on 06 Jul 2023
186 points (97.9% liked)

Fediverse

28489 readers
613 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 2 years ago
MODERATORS
 

I strongly encourage instance admins to defederate from Facebook/Threads/Meta.

They aren't some new, bright-eyed group with no track record. They're a borderline Machiavellian megacorporation with a long and continuing history of extremely hostile actions:

  • Helping enhance genocides in countries
  • Openly and willingly taking part in political manipulation (see Cambridge Analytica)
  • Actively have campaigned against net neutrality and attempted to make "facebook" most of the internet for members of countries with weaker internet infra - directly contributing to their amplification of genocide (see the genocide link for info)
  • Using their users as non-consenting subjects to psychological experiments.
  • Absolutely ludicrous invasions of privacy - even if they aren't able to do this directly to the Fediverse, it illustrates their attitude.
  • Even now, they're on-record of attempting to get instance admins to do backdoor discussions and sign NDAs.

Yes, I know one of the Mastodon folks have said they're not worried. Frankly, I think they're being laughably naive >.<. Facebook/Meta - and Instagram's CEO - might say pretty words - but words are cheap and from a known-hostile entity like Meta/Facebook they are almost certainly just a manipulation strategy.

In my view, they should be discarded as entirely irrelevant, or viewed as deliberate lies, given their continued atrocious behaviour and open manipulation of vast swathes of the population.

Facebook have large amounts of experience on how to attack and astroturf social media communities - hell I would be very unsurprised if they are already doing it, but it's difficult to say without solid evidence ^.^

Why should we believe anything they say, ever? Why should we believe they aren't just trying to destroy a competitor before it gets going properly, or worse, turn it into yet another arm of their sprawling network of services, via Embrace, Extend, Extinguish - or perhaps Embrace, Extend, Consume would be a better term in this case?

When will we ever learn that openly-manipulative, openly-assimilationist corporations need to be shoved out before they can gain any foothold and subsume our network and relegate it to the annals of history?

I've seen plenty of arguments claiming that it's "anti-open-source" to defederate, or that it means we aren't "resilient", which is wrong ^.^:

  • Open source isn't about blindly trusting every organisation that participates in a network, especially not one which is known-hostile. Threads can start their own ActivityPub network if they really want or implement the protocol for themselves. It doesn't mean we lose the right to kick them out of most - or all - of our instances ^.^.
  • Defederation is part of how the fediverse is resilient. It is the immune system of the network against hostile actors (it can be used in other ways, too, of course). Facebook, I think, is a textbook example of a hostile actor, and has such an unimaginably bad record that anything they say should be treated as a form of manipulation.

Edit 1 - Some More Arguments

In this thread, I've seen some more arguments about Meta/FB federation:

  • Defederation doesn't stop them from receiving our public content:
    • This is true, but very incomplete. The content you post is public, but what Meta/Facebook is really after is having their users interact with content. Defederation prevents this.
  • Federation will attract more users:
    • Only if Threads makes it trivial to move/make accounts on other instances, and makes the fact it's a federation clear to the users, and doesn't end up hosting most communities by sheer mass or outright manipulation.
    • Given that Threads as a platform is not open source - you can't host your own "Threads Server" instance - and presumably their app only works with the Threads Server that they run - this is very unlikely. Unless they also make Threads a Mastodon/Calckey/KBin/etc. client.
    • Therefore, their app is probably intending to make itself their user's primary interaction method for the Fediverse, while also making sure that any attempt to migrate off is met with unfamiliar interfaces because no-one else can host a server that can interface with it.
    • Ergo, they want to strongly incentivize people to stay within their walled garden version of the Fediverse by ensuring the rest remains unfamiliar - breaking the momentum of the current movement towards it. ^.^
  • We just need to create "better" front ends:
    • This is a good long-term strategy, because of the cycle of enshittification.
    • Facebook/Meta has far more resources than us to improve the "slickness" of their clients at this time. Until the fediverse grows more, and while they aren't yet under immediate pressure to make their app profitable via enshittification and advertising, we won't manage >.<
    • This also assumes that Facebook/Meta won't engage in efforts to make this harder e.g. Embrace, Extend, Extinguish/Consume, or social manipulation attempts.
    • Therefore we should defederate and still keep working on making improvements. This strategy of "better clients" is only viable in combination with defederation.

PART 2 (post got too long!)

top 50 comments
sorted by: hot top controversial new old
[–] Gradually_Adjusting@lemmy.world 8 points 1 year ago (24 children)

Defed every corporation. McDonald's starts an instance? Fuck off and fix your ice cream machine. Gabe Newell starts a Steam instance? No Gabe, go make half life 3. Make all these suits federate each other and see if anyone wants to talk on their shit.

[–] sapient_cogbag@infosec.pub 6 points 1 year ago (2 children)

Meta in particular has a specific record of social manipulation, which is why I think defederating them specifically is so important. Even if we collectively have mixed feelings on corporate instances in general, social media companies, especially those like Facebook, have a specific and direct record of manipulating people and the population nya. Facebook/Meta in particular, is probably the worst of any of them.

Meta might be the worst possible company to darken our doorstep; at least Elon would fail.

[–] intensely_human@lemm.ee 2 points 1 year ago* (last edited 1 year ago)

Yes, reputation is very important. The cluster of people known as Meta has proven it is nefarious at best.

It's good to consider the case-by-case basis instead of just making general rules.

Like if Lowes wanted to make an instance I wouldn't worry much about its corporate influence. But Meta is actually an evil organization.

(Though their React docs are some of the best docs I've ever read)

[–] kratoz29@lemmy.world 2 points 1 year ago (1 children)

No Gabe, go make half life 3.

This make me chuckle.

[–] Bushwhack@lemmy.world 1 points 1 year ago

I mean, they aren’t fucking wrong. Half life 3 has a federated communication system built into multiplayer? Go do it Gabe.

[–] DarkMatter_contract@lemmy.world 1 points 1 year ago (1 children)

I dont think mastodon would, but i think lemmy kbin would. The target audience is different, one is twitter and the other is reddit like. I dont think twitter user hate fb as much as we do.

They always did strike me as idiots

load more comments (21 replies)
[–] Candelestine@lemmy.world 3 points 1 year ago (2 children)

We will never be able to compete with them for as long as they remain federated with us. We will simply have no unique value any longer. All of our development--open source. All of our content--available to the federation. He will have rightful possession of it all, everything we are.

However, he does not have to share his development with us. He does not have to share his hardware resources with us. He does not have to limit himself to only the capabilities that we want to be added.

He can, if absolutely necessary, buy us. One big Instance at a time.

Our only path forward with any independence is to defederate immediately and ruthlessly. This way, we keep our content. We keep that unique contribution, that we can use as a competitor to eventually demonstrate our value to the rest of the world. That's the only way possible for us to have any chance of eventually toppling him, instead. We must retain our unique value. We must protect our content. If he wants it, make him scrape it and repost it with bots or something.

[–] Buddahriffic@lemmy.world 1 points 1 year ago

Another option is to make migration of everything from one instance easy and let them buy whichever instances they want but let the users go somewhere else. Turn their weaponized capitalism into free money for instance admins until they wisen up and stop throwing money at it.

Or set up the terms and services to give the instances responsibilities that must be honoured even after they get purchased by another entity such that buying them becomes unattractive. Like mandate a certain portion of the topmost parent company's profits (along with clauses to prevent Hollywood accounting from dodging that, maybe say revenue instead of profit and all related companies instead of just the topmost) must be invested back into the fediverse and that changing the TOS to remove that requires a certain number of users to agree. Set it up so that it is designed to only work if the whole point of the entity is to host a community rather than extract profit from hosted communities.

[–] Thorny_Thicket@sopuli.xyz 0 points 1 year ago* (last edited 1 year ago) (2 children)

Even if we defederate with them they can still grab all the content here. Defederation just stops the flow of content from their instance to ours. Defederation just hides the comments from Threads' users on our discussions.

I think the real test is when they start demanding that other instances start moderating their content to comply with Facebook's terms of service and if not then defederate and make them unable to communicate with the by-far biggest instance on the fediverse with almost all the users.

load more comments (2 replies)
[–] sapient_cogbag@infosec.pub 3 points 1 year ago* (last edited 1 year ago) (1 children)

The post is too big for my next edit, so here is the next edit in a comment:

Edit 2 - Clarification, Expanding on Facebook's Behaviour, Discussion of Admin-FB Meetups

I want to clarify the specific dangers of Meta/FB, as well as some terminology.

Embrace, Extend, Extinguish, and Embrace, Extend, Consume

The link I posted approximately explains EEE, but in this thread I've used the phrase "Embrace, Extend, Consume", to illustrate a slightly modified form of this behaviour.

Embrace, Extend, Consume is like Embrace, Extend, Extinguish except the end goal isn’t complete annihilation of the target. Instead of defederating at the endpoint, Meta/FB just dominates the entire standard, and anyone who steps out of line is forced into a miniscule network of others.

They can then use this dominant position to buy out or consume large instances, or for example, force data collection features into the standard and aggressively defederate anyone else who doesn’t comply >.< - because they're so big, most instances will comply in the service of "content".

Such a dominant position can even be obtained simply by sheer user mass, which Threads already has to some degree, as long as the relevant instance has large amounts of financial resources to buy out instances.

In this way, they consume the network entirely, which doesn’t necessarily destroy the communities but essentially Borg-ifies them and renders people unable to leave their grasp.

Facebook/Meta-Specific Threats: Information Warfare & Manipulation

One of the major specific threats of Meta/FB in particular is their long and continued history of engaging in what essentially amounts to large-scale psychological manipulation and information warfare towards it's various goals (money, total domination of human communication, subsuming the internet in countries where the infrastructure is still too small to resist a single corporation restricting it's content, political manipulation, collection of ever more data, etc.), against both it's users and non-users.

They have well over a decade of experience in this, hundreds of times more users than us (providing good cloaking for astroturfers), and untold amounts of labour, research and other resources have been poured specifically into figuring out the most effective ways to manipulate social groups via techniques like astroturfing, algorithmic prioritization, and more sophisticated strategies I am not aware of. All backed by data from literally billions of human beings >.<

This means that exposing the Fediverse to Facebook/Meta is essentially exposing us all to one of the most organised and sophisticated information warfare machines that has ever been created. Cutting off the connections immediately (as in the other analogy by @BreakingBad@lemmy.world) not only protects from direct EEE/EEC, but also makes it harder for Meta/Facebook to influence, dominate, and consume the conversation here, either by sheer user-mass, or by malicious information warfare (or even unintentional consequences of their algorithms), or by a combination of all of these.

We know they are extremely malicious and willing to use these methods towards real-life, ultra-harmful ends. Examples are at the start of this post :)

For hypothetical examples on how this might work - in reality it might be different in the specifics (these are just illustrative):

  • Meta/FB could start a campaign (maybe astroturfed) for "user safety", where they encourage people to distrust users from smaller instances or any user with their instance address marker not on @threads.
  • Meta/FB could add "secure messaging" (lol, it's facebook), but only between threads users. Then they could push the idea that ActivityPub is bad for privacy (the DMs are, but just use Matrix ;p - if you post stuff publicly, it makes sense that it's public).
  • Meta/FB could by simple user mass result in most communities being on Threads. People tend to drift towards more populous communities about the same topic, in general, and Threads unbalances the user ratios so much that everyone would just go to those >.< (as opposed to right now, where we have similar sized communities on several large instances, where most people subscribe to most of them)
  • Meta/FB could use social engineering to push for changes to the ActivityPub protocol that are harder for other ActivityPub servers to implement ^.^, or even ones that are hard for non-proprietary clients to implement. For example, embedding DRM in the protocol or something like that.
  • Meta's algorithms could over time shift towards deprioritising non-"paid"/"verified" Threads users.
  • It's already been explained how the app as we know it essentially makes it hard for people to leave due to the fact only they have access to their server software and they also ensure that the app is only a specific client for this service.

Instance Admins, and the "Friendliness" of Meta

Some instance admins have been in contact with Meta/FB. It does make sense for at least some of them to do "due dilligence", but I've seen in at least one post a comment on the friendliness and cooperativeness of the engineers and the fact they mostly discussed architectural concerns and stuff like moderation and technical stuff.

I want to remind instance admins that no matter how nice the engineers are - and how much they share your interests - they are still working for what is essentially a mass information warfare machine. This doesn't make them malicious at all, but it does mean that what they are doing is not a solid perspective on the actual goals and attitude of Meta/Facebook, The Corporate Assimilator Organism.

Regardless of what they have discussed, they are obligated as employees to act on Meta's orders, not the things they actually want to work on or the things both them and you find important ^.^ - or even act towards the goals they want to act towards when Meta inevitably goes for the throat.

I encourage instance admins to keep this in mind, and further keep in mind that Meta is pretty much royalty when it comes to social stuff and how to appeal to people. If they were trying to appeal to a more corporate social media service, they'd probably have gone with sending in the C-suite, but they know this community is technically inclined and less likely to buy into corpo speak and corpo bullcrap, so they probably hooked you up with all the chill engineers instead :).

Reiterating my view: Resist Corpo-Assimilation!

Note on This Post

I've realised this post would probably be most useful if the primary targets of Threads could see it (Mastodon). But I don't have Mastodon cus I really am not into microblogging myself, so RIP ;p

we need to force defederation from thread's

[–] goetzit@lemmy.world 3 points 1 year ago (3 children)

The craziest thing to me is that people seem to be lining up to make excuses for Meta. We learned the first week of this migration that defederating can get messy, we saw it right away with Beehaw.

Had Beehaw defederated from the larger instances sooner, then there would have been no outrage in the community over it. But while Lemmy was seeing a lot of growth, a lot of the big communities were being made on beehaw. All of the sudden, people were unable to access these communities properly and they were PISSED.

Guys, look around! Threads has what, 10 million users already? We have like, a hundred thousand, maybe a few hundred thousand at best? They will no doubt have huge communities formed by the time they decide they want to start federating. The ratio of Lemmy/Kbin users to threads users will be 100:1.

If we federate with Meta we basically have no choice but to use the communities they host. People only want to use 1 community (the issue of duplicate communities is brought up daily), so they will flock to the largest one. When Meta decides they don’t want to play nice with us anymore (and they will, it is never profitable to let people access all your content completely free, and shareholders will come knocking), defederation is going to decimate whats left here. Personally I think the place would implode, and many would migrate to where the content is.

[–] bezerker03@lemmy.bezzie.world 1 points 1 year ago

Ultimately this is the thing to worry about. Threads will get the largest communities and as a result the main amount of attention and when/if Meta decides to defederate, it will ruin things. Also, people will generally give zero shits about federation because 99.9% of content will be on meta's instance.

Ironically, the main thing keeping fediverse from being more popular (the decentralized approach and "multiple places the same community can exist") are going to be the thing that kills it if Meta gets involved and becomes the big boy.

Idunno what is arguably worse. The fediverse being restricted to more "technical" folks who give a shit, and thus a far more limited audience than a central platform, or being suddenly disconnected from the hivemind after taking all the content.

(Fwiw, I absolutely think that the Threads fediverse plan is to totally absorb all the content and become the main place for it then possibly pull the plug but honestly at that point they won't even need to the usage stats will basically do the same thing for them.)

load more comments (2 replies)
[–] Mikina@programming.dev 2 points 1 year ago

Definitely defederate. I did not come here to let Meta monetize my content on their platform. Also - Facebook and Instagram crowd is among the worst userbase on the internet, with the blandest cotent, right behind Tik-Toc. I don't think it has much value, and it would make everything hell to moderate - it's just a lot of users.

So, defederate, I say.

[–] ubergeek77@lemmy.ubergeek77.chat 2 points 1 year ago* (last edited 1 year ago)

Not only did I add threads.net to my blocked instances list, I also went scorched Earth and outright blocked Facebook's entire IP range through my firewall. Don't want them "accidentally" reading any data from my server ;)

For reference, their IP range is 157.240.0.0/16:

Edit: Actually, I might have more IPs to block:

https://whois.arin.net/rest/org/THEFA-3/nets

[–] Dax0Lotl@lemmy.sdf.org 2 points 11 months ago* (last edited 11 months ago)
[–] kiwiheretic@lemmy.ca 1 points 1 year ago

I thought I would just chime in here if I am allowed. I looked for an official Facebook lemmy but couldn't find one.

I have become a bit satisfied with Facebook as of late. They used to allow tools for embedding social pages into private websites and whilst technically they still do their level of support for such seems to have plummeted to non existent. I don't know if that is a conscious effort by Meta to close down forum support or whether it is because they are moving more towards a "pay to play" business model. This in, my opinion, suddenly erects a huge barrier to entry, to even get started developing with their platform. It would seem to me it would have been more prudent, as a business model, to provide free support to get started but start charging when their products are established or at least have some way to talk to a support person.

What I am saying, in a roundabout way, is maybe the world is ready for a decent alternative, even in the business space, and Facebook no longer seems to be it. I really can't understand how their support has collapsed so badly for developers.

[–] ToastyMedic@reddthat.com 1 points 1 year ago

For what it's worth, I'd like to put my voice. Out here in support of defederating them.

Our goals and their goals are like parallel Lines, They'll never cross.

[–] ComptitiveSubset@lemmy.world 1 points 1 year ago

OP is correct. We have very little to to gain and everything to lose.

[–] Yoz@lemmy.world 1 points 1 year ago

Ban meta and its instance on a firewall level

[–] EqMinMax@lemmy.world 1 points 1 year ago (1 children)
[–] zloubida@lemmy.world 1 points 1 year ago

XMPP is still alive, and is just what it was before Google used it. I don't understand this argument.

[–] Quinnel@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

A problem I haven't seen anyone discuss: What of server costs?

When even just 1% of the still growing 30 MILLION Threads users (300k) are interacting with an average Mastodon, Lemmy, etc. instance every day, just how much data do you think that will generate? As Threads scales and users are posting content that users on smaller instances try to interact with, the hosts of these smaller instances bear the brunt of the costs.

Threads need only exist, and as everything scales upward and more people join the Fediverse, their sheer mass will wipe out all the smaller players just by virtue of the smaller servers being unable to cover growing server costs. 300k users creating 1kb of content each, per day, comes out to 292 megabytes of data. (But that's not realistic. The OP contains 5,171 characters, or roughly 5kb of data.) This does not account for images, or videos, which also cost money to store. If 1% of those 300k users (1% of the 1%, 3,000 people out of 30 million) are posting images, if we assume the maximum file size Mastodon can store (8mb per image) and arbitrarily set the file size at 1mb to try to be conservative, we're still adding an additional 3,000 megabytes of data per day in addition to the original 292, or 3.21 gigabytes of data. We're not even yet accounting for the additional data to store the database references for all of this either, keep in mind.

Those numbers are small. They don't include videos, and they vastly underestimate the amount of users interacting with any of our smaller instances. Every time a reply containing an image or video is posted to Threads, if smaller instances want to keep a copy for their own users to reply to or interact with, they have to store that data.

Server owners will be buried under the server costs -- costs which Meta can easily subsidize with Instagram and Facebook revenue, not unlike Walmart intentionally under-pricing everything in a new branch in a small town right up until every local store ceases to exist, at which point they jack up the prices and put another new store somewhere else.

[–] YellowtoOrange@lemmy.world 1 points 1 year ago

Good points. The musings of Lemmy/kbin/other users will be lost in the mass of karen posts, soccer moms, extremist views, god knows what else.

It's pretty obvious that those who came here from Reddit or wherevee are looking for a place that is not dictated to by commercial interests, and if threads attaches onto these communities, I guess we'll leave for somewhere else.

[–] jasonbcfcufc@lemmy.world 1 points 1 year ago

is there a good twitter app out there instead of the original for android?

[–] cley_faye@lemmy.world 1 points 1 year ago

I'm still baffled that some people can argue "why are you so worried?" about this. We have twenty years of history of shit hitting the fan, how much more do you need to not trust Facebook/Meta?

[–] Coelacanth@feddit.nu 1 points 1 year ago (3 children)

By sheer user count allowing them to federate would mean the end of non-Meta content on the All feed. Threads is already much bigger than the entire combined Fediverse so the total engagement would drown any Lemmy content, unless of course driven by Meta comments itself. This would no longer be Lemmy, it would be Threads that you could use your Lemmy account for. Maybe not if the algorithm was changed to filter out posts from Threads from the All feed, but you'd still get your communities flooded with Facebook comments.

This is in addition to the rest of the problematic issues with Meta as a company.

[–] Hikiru@lemmy.world 1 points 1 year ago

I’m fine with threads federating with mastodon as it means more content which means people won’t immediately dismiss mastodon because it’s too boring for them, but I don’t want Lemmy to federate with Lemmy any more than I want to read tweets on reddit. They’re different types of platforms for different things.

[–] Resonosity@lemmy.world 1 points 1 year ago (1 children)

Users can still block instances though with Lemmy, yeah? So even if admins of instances don't block Threads, I'd imagine users would be able to. Maybe I'm misinterpreting the capabilities of the software, however.

[–] Coelacanth@feddit.nu 1 points 1 year ago* (last edited 1 year ago)

You can block communities at user level but not whole instances yet, it's been requested as a feature I think, though.

[–] pezhore@lemmy.ml 1 points 1 year ago

This is what I've been thinking lately. There's no way to unring that bell after an influx of several million people "join" Mastodon through Threads.

Plus threads has an entire team of engineers who can be abused to get out better looking apps, sys admins who ensure the threads servers are running at minimal load - ensuring a top tier Fediverse experience. Already we've seen a burst of indie developers for Lemmy and Mastodon, but what if I'm not concerned that my microblog app needs to know health biometric data - threads is up when my niche instance goes down.

That's how they get you. Come to threads for a "better user experience"! You can still follow the weird Bean memes, but with a better UI/UX! Don't worry, we at Facebook won't defederate with everyone else once we hit critical mass!

[–] Wr4ith@lemmy.world 1 points 1 year ago

Reddit and twitters recent moves were the driving force behind me switching to mastadon and lemmy, but I ditched meta/Facebook services long ago. Adding those back into this fold really makes the choice for me kind of easy. Inviting meta to the party is just a non starter.

[–] phil299@lemmy.world 0 points 1 year ago (1 children)

My gut tells me we should defed all corporate instances as a matter of policy. Our uniqueness is at jeopardy , think of threads like the borg.

[–] WizzCaleeba@lemm.ee 1 points 1 year ago

Obligatory upvote for Star Trek reference That's the beauty of individual servers, isn't it? If you're on an instance that doesn't defend those corporate instances, but want to, them just move to one that does. The voices will speak.

load more comments
view more: next ›