How to Kill a Decentralised Network (such as the Fediverse)
ploum.net
How to Kill a Decentralised Network (such as the Fediverse) écrit par Ploum, Lionel Dricot, ingénieur, écrivain de science-fiction, développeur de logiciels libres.

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!)

  • sapient [they/them]@infosec.pubOP
    904·
    1 year ago

    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.<whatever their url>
    • 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