Why Defederating from Facebook/Meta is So Important

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.

https://infosec.pub/comment/653611 (post got too long!)

A digital speedpainting. A giant reaper with a golden chain around their neck with the logo of Facebook, Instagram and WhatsApp and a headband with the meta logo. The giant silhouette surprise a tiny group in comparison; a warm scene of small cute characters gathered around a Fediverse glowing logo. This is the mascott of Mastodon, Pleroma, Misskey, Funkwhale, Lemmy, Peertube.

This is my feelings in reference to the discussions about Meta joining the Fediverse...

License: CC-By 
(except logo of Meta/Facebook/What'sApp and Instagram, under trademarks)
Quinnel,

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,
@YellowtoOrange@lemmy.world avatar

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.

rs137,

I’m all for defederation. It might seem alright in the beginning but slowly the problems would arise to a point that being on Facebook’s Threads would be easier. At that point they won because the rest of Fediverse would be deserted and thus killed. Just remember what happened with XMPP and Google Talk. It’s so incredibly sad that the Internet feels like a battlefield again. We free users who would like to enjoy a nice service without any enshittification and without being commodified vs another faceless corporation that would like to make money out of us all.

sapient_cogbag,
@sapient_cogbag@infosec.pub avatar

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

sapient_cogbag,
@sapient_cogbag@infosec.pub avatar
Zstom6IP,

Lemmy is federated with facebook?

Draconic_NEO,
@Draconic_NEO@lemmy.world avatar

Their new Twitter clone, “Threads” will likely attempt to federate with Mastodon, and therefore Lemmy and kbin unless instance operators decide to defederate their service, possibly preemptively if we can.

In my opinion they absolutely should do that there’s not much good that will come out of being Federated with a Facebook/Meta product and an insane amount of bad things that will come out of it, we need to nip this in the bud just like we did with Gab (though I will admit that was for different reasons).

Zstom6IP,

i agree, but will there be a way to avoid the facebook shithole twitter?

Draconic_NEO,
@Draconic_NEO@lemmy.world avatar

Defederating is a pretty good solution, it stops them from being able to directly communicate with your servers, preventing them and their users from posting on the instances that they have been defederated from. One example of a server that will be doing this is pawb.social I’m sure others will follow as well.

I’m not sure if it would be necessary but you could also go the extra mile and block their IP range at the firewall level on your Lemmy server. That’s mainly something that you would do for spammers, but since Facebook/Meta do have a bad track record it couldn’t hurt.

sapient_cogbag,
@sapient_cogbag@infosec.pub avatar

Not yet. And hopefully most of the instances decide to pre-emptively defederate.

Zstom6IP,

Do you think it will happen?

sapient_cogbag,
@sapient_cogbag@infosec.pub avatar

Most of Lemmy and the associated instances seem to be very anti-Meta so far. I think it’s not likely for lemmy as a whole, though we might see a minority of instances that federate with Meta. Got to wait and see ^.^

Mastodon I’m somewhat more worried about.

Zstom6IP,

Where does lemmy.world stand on this?

dutchkimble,

I’m imagining Zuckerbot finding your post and his eye screen going red and it has your name and photo with a big flashing red PRIMARY TARGET

Eienkei,

There’s nothing good coming out of Facebook or any for-profit public enterprise. F* Zuck, Musk & all billionaire scums.

Bleach7297,
@Bleach7297@lemmy.ca avatar

I’ll probably keep a presence on a non-threads-federated instance and one on a threads-federated instance, just to compare and to talk to grandma. I doubt I’ll spend much time scrolling through whatever it is Instagram users write about but you never know.

TheRealBob,
@TheRealBob@lemmy.world avatar

Frankly, I think they’re being laughably naive >.<

The creator of Mastodon went to some kind of Meta round table meeting (couldn’t find the original thread, here’s someone declining the offer), so it’s entirely possible that he was told a bunch of lies and believed them.

That said, Meta is going to pay the admins of whatever instances Threads decides to federate with, and they’ve said that’ll be the biggest instances, which… well, that’s mastodon.social, by far the biggest Mastodon instance. So, I don’t know. I don’t have any reason to believe that he’s a bad person, but what kind of money are we talking about here? No one is immune to that kind of temptation.

I dunno, this whole situation has a weird vibe.

Rengoku,

If mastodon.social is the biggest instance, threads have been laughing for their number since the first day it was released.

Meta do not need Mastodon users at all to take off. They dont even federate at the moment.

minnow,

You’re 100% correct, but don’t think that’s enough for Meta. It’s inherent to the nature of corporations to sell to grow, ie increase market share. If Meta thinks it can increase it’s market share, even a little, by destroying mastodon.social it will.

Melco,

deleted_by_author

  • Loading...
  • sapient_cogbag,
    @sapient_cogbag@infosec.pub avatar

    github.com/wescode/lemmy_migrate

    For now, this is the best I’ve found. I think there’s work on implementing this in actual lemmy, but this python script is the best option I know of ^.^ - you basically put your user account name and password for each account in a config file and run the script - though I’d make sure to delete the config file after you’ve done it, preferrably with some kind of secure-delete tool like shred on linux.

    However, we don’t know yet if lemmy.world will defederate from Meta/FB, until the admins make some kind of statement on it nya. So I wouldn’t leave yet. Though making an account on a smaller instance might be a good idea anyway for simple performance reasons :)

    Draconic_NEO,
    @Draconic_NEO@lemmy.world avatar

    Maybe it might be a good idea for people to reach out to the admins of lemmy.world and other instances about this issue. The sooner we know the better. Might be worth making a post on the main Communities of instances such as !lemmyworld and !main as well as a few others about these issues.

    Sturgist,
    @Sturgist@lemmy.ca avatar

    I made this lemmy.ca account today because the admins stated specifically that they will defed and block meta. I moved from a larger instance, but that account only had a month and a bit of history to it, and I have no issue just closing up shop there.

    not_that_guy05,

    Hold on, is Lemmy part of meta? Cause if it is I’m fuckin out of here as well. I do not support meta fb, or any other company like them.

    khazram,
    @khazram@mastodon.social avatar

    @not_that_guy05 No. Lemmy is not owned by any corporation or any one person. All that federation or defederation means is whether an instance connects to another.

    not_that_guy05,

    Oh ok. I really hope they don’t allow it then. Meta is a cancer that grows once inside a body(platform).

    intensely_human,

    I’m having trouble conceptualizing the attack strategies here. I also lack much understanding of what (exactly, precisely, at the technical level) federation is so I don’t understand how defederation is a defense against those attacks.

    Would someone help me break this down conceptually? Are there any analogies? Is this like closing the gate of a castle? Is it like quarantining infected people? Like blocking a phone number? Not loaning someone money?

    Please don’t just say “yes to all those analogies”. I’m casting about for understanding here.

    How can I better understand OP’s argument here? (I have a background in tech and understand passwords, certificates, signatures, etc if that helps). Is email a federated thing? What’s federation precisely?

    BreakingBad,

    Layman here, from what I gather it sounds like federation is like one of those cups connected by lines. Federation is the equivalent of having a line connected to the web of cups and strings. Then suddenly a big cup provider comes into the mix, which at first seems great since there are more people communicating through cups. However, due to their bigger resources they greatly outpace the rest of the web, offering fancier cups and stronger wire, resulting in people moving to their cups. Then one day they cut the connections to all other cups but theirs; while the original web is still intact, the remaining users are essentially cut off from most of the cups they were connected for.

    By defederating instances are basically (but probably not as effectively as Meta would) cutting that string before they get the chance to infiltrate the web.

    Idk though once again I know very little

    rockSlayer,

    For “knowing very little”, you fucking nailed that analogy. That’s exactly what Instagram is trying to pull here.

    sapient_cogbag,
    @sapient_cogbag@infosec.pub avatar

    Someone has explained the basic Embrace, Extend, Extinguish strategy below, but I also want to comment on my own “Embrace, Extend, Consume” idea, as well as the other issues that come with Facebook.

    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 >.<

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

    The other component specific to facebook 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.).

    They have well over a decade of experience in this, hundreds of times more users, 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 strings (as in the other analogy by @BreakingBad) 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 both.

    For hypothetical examples on how this might work - in reality it might be different in specific, 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 so just use Matrix ;p, but 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.
    intensely_human,

    So it’s like opening a wormhole to the borg homeworld. Not worth the effects of contact.

    Xanvial,

    I think I miss something, the ActivityPub protocol is not owned or maintained by Mastodon devs. Isn’t this just standard communication like an extension of HTTP? something like GraphQL (that created by Facebook itself). Quick google mentioned that ActivityPub is maintained by W3C.

    So Meta can (and I think currently uses) ActivityPub, and all of your points already been possible without needing to federates with any other instances. For example, they already can say that ActivityPub doesn’t work on some cases, and push W3C to do some changes on the standard

    minnow,

    I think the critical difference is “Meta pushes for changes” vs “Meta pushes for changes with the support of thousands/millions of users”.

    If Meta convinces Thread users that a certain change is good for them, it’s going to be that much harder for the people developing ActivityPub to push back on those changes. And even if the developers succeed, Meta can just use that to say “fine, we’ll fork off and make our own ActivityPub with data collection and advertisements” and if enough instances in the Fediverse are reliant one Threads for engagement they may just switch to the Meta version of ActivityPub, taking a chunk of our community with them.

    And maybe that’s alright for some folks, but a lot of us don’t want any of that to happen, even potentially. I think it’s pretty unethical to deliver people into the maw of the beast like that, so to speak.

    Marxine,
    @Marxine@lemmy.world avatar

    Bravo. This goes straight to the main goal of Meta: they want us exposed to their manipulation, their astroturfed content and their psychological traps. They want our attention to their content, and the best defense we can have is negating them from having any of it.

    wavymoney,

    Seal the doors! Mark/Meta’s obsession over user base and data control has to be put in check. They’re like a social culture vulture. Riding the next wave but the attempt ends up being stale, killing the mood for everyone that just wanted to enjoy something to themselves.

    warmaster,

    Meta can Zuck it.

    iDunnoBro,

    It’s guaranteed that they’ll use their instance to datamine and further build profiles on people in other federated instances as well.

    I don’t trust them at all with their handling of data besides their ability to track people who aren’t even on their platforms. Also it’s almost impossible to reach out to them unless you buy their shitty VR headset, as you will find out if someone ever fraudulently takes your account to buy ads with your money and gets your FB account banned.

    Fuck the Zuck.

    Semenaisse,

    I’m still getting used to this platform, so this might be a stupid question. Are we able to see their content/can they see ours?

    sapient_cogbag,
    @sapient_cogbag@infosec.pub avatar

    If we defederate, they can technically pull our content because it’s public, but it’s difficult, and their users won’t be able to interact with it.

    We would not be able to see theirs unless you manually went to their site.

    Right now, they still haven’t turned federation on, so we can’t do that. If we do federate, we will be able to (easily) see and interact with their content, and they will be able to (easily) see and interact with our content. If we defederate, we can technically see each other’s content by visiting their site (or them visiting ours), but we wouldn’t be able to usefully interact with them and vice-versa without making an account on their site (or vice-versa) ^.^

    klieg2323,
    @klieg2323@lemmy.piperservers.net avatar

    Why wouldn’t they be able to interact with it, at least within their own ecosystem? The way I understand, if I defederate with them on my instance they can still see my content but I can’t see theirs. There’s nothing stopping Metta from taking that public data anyways and allow only their users to interact with it in their own sealed space. With how many users they have, it’s possible it wouldn’t even be noticed by the average threads user

    sapient_cogbag,
    @sapient_cogbag@infosec.pub avatar

    Why wouldn’t they be able to interact with it. The way I understand, if I defederate with them on my instance they can still see my content but I can’t see theirs. There’s nothing stopping Metta from taking that public data anyways and allow only their users to interact with it in their own sealed space. With how many users they have, it’s possible it wouldn’t even be noticed by the average threads user

    Well, theoretically we could do the same. Host shadow-Threads content. That’s essentially what’s going on with reddit repost-bots, after all. But if you look at those they usually have no comments and for Facebook in particular, I would argue that enabling their ability to spread their content to the Fediverse is dangerous even if we don’t interact with it.

    And the same is true for Threads - they could actually do that kind of re-posting, in theory, but then it’s pretty much just them reposting a link to some post on the Fediverse with their own silo. We wouldn’t see any of them at that point. I’m arguing for defederating on the basis that it protects us from Meta/Facebook, not on the basis that it would stop Threads users from seeing some parts of Fediverse content (essentially posted as links) ^.^.

    intensely_human,

    I would argue that enabling their ability to spread their content to the Fediverse is dangerous even if we don’t interact with it

    How is it dangerous?

    sapient_cogbag,
    @sapient_cogbag@infosec.pub avatar

    Meta/Facebook has 100s of times the number of users, many more times the amount of resources, the constant desire to consume other platforms like Instagram and whatsapp (or destroy the a-la Embrace, Extend, Extinguish), and well over a decade of experience in engaging in manipulation and essentially, information warfare, to get what they want and commit hienous behaviour.

    Even just the quantity of users on a single, difficult to exit instance is a risk, but the continuous and long history of Facebook engaging in largescale psychological manipulation makes them many times more dangerous ^.^

    In particular, you looking at their algorithmically curated posts enables them to manipulate you with their decades of refined, algorithmic experience in doing so, as they have repeatedly done in the past.

    intensely_human,

    So basically their content is dangerous. Even if it’s user-generated, it can be machine-curated for psychological manipulation. What seems like a natural flow of conversation could be a signal used to hack our minds.

    I’m not trying to make it sound crazy by wording it that way. There are people in my life I just had to cut out because their speech was toxic to my mental health in a way I couldn’t rationally object to. I just had to stop listening to them.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • uselessserver093
  • Food
  • aaaaaaacccccccce
  • [email protected]
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • Socialism
  • KbinCafe
  • TheResearchGuardian
  • Ask_kbincafe
  • oklahoma
  • feritale
  • SuperSentai
  • KamenRider
  • All magazines