A Brief Primer on Technofascism

Introduction

It has become increasingly obvious that some of the most prominent and monied people and projects in the tech industry intend to implement many of the same features and pursue the same goals that are described in Umberto Eco’s Ur-Fascism(4); that is, these people are fascists and their projects enable fascist goals. However, it has become equally obvious that those fascist goals are being pursued using a set of methods and pathways that are unique to the tech industry, and which appear to be uniquely crafted to force both Silicon Valley corporations and the venture capital sphere to embrace fascist values. The name that fits this particular strain of fascism the best is technofascism (with thanks to @future_synthetic), frequently shortened for convenience to techfash.

Some prime examples of technofascist methods in action exist in cryptocurrency projects, generative AI, large language models, and a particular early example of technofascism named Urbit. There are many more examples of technofascist methods, but these were picked because they clearly demonstrate what outwardly separates technofascism from ordinary hype and marketing.

The Unique Mechanisms of Technofascism

Disassociation with technological progress or success

Technofascist projects are almost always entirely unsuccessful at achieving their stated goals, and rarely involve any actual technological innovation. This is because the marketed goals of these projects are not their real, fascist aims.

Cryptocurrencies like Bitcoin are frequently presented as innovative, but all blockchain-based technologies are, in fact, inefficient distributed database based on Merkle trees, a very old technology which blockchains add little practical value to. In fact, blockchains are so impractical that they have provably failed to achieve any of the marketed goals undertaken by cryptocurrency corporations since the public release of Bitcoin(6).

Statement of world-changing goals, to be achieved without consent

Technofascist goals are never small-scale. Successful tech projects are usually narrowly focused in order to limit their scope(9), but technofascist projects invariably have global ambitions (with no real attempt to establish a roadmap of humbler goals), and equally invariably attempt to achieve those goals without the consent of anyone outside of the project, usually via coercion.

This type of coercion and consent violation is best demonstrated by example. In cryptocurrency, a line of thought that has been called the Bitcoin Citadel(8) has become common in several communities centered around Bitcoin, Ethereum, and other cryptocurrencies. Generally speaking, this is the idea that in a near-future post-collapse society, the early adopters of the cryptocurrency at hand will rule, while late and non-adopters will be enslaved. In keeping with technofascism’s disdain for the success of its marketed goals, this monstrous idea ignores the fact that cryptocurrencies would be useless in a post-collapse environment with a fractured or non-existent global computer network.

AI and TESCREAL groups demonstrate this same pattern by simultaneously positioning large language models as an existential threat on the verge of becoming a hostile godlike sentience, as well as the key to unlocking a brighter (see: more profitable) future for the faithful of the TESCREAL in-group. In this case, the consent violation is exacerbated by large language models and generative AI necessarily being trained on mass volumes of textual and artistic work taken without permission(1).

Urbit positions itself as the inevitable future of networked computing, but its admitted goal is to technologically implement a neofeudal structure where early adopters get significant control over the network and how it executes code(3, 12).

Creation and furtherance of a death cult

In the fascist ideology described by Eco, fascism is described as “a life lived for struggle” where everyone is indoctrinated to believe in a cult of heroism that is closely linked with a cult of death(4). This same indoctrination is common in what I will refer to as a death cult, where a technofascist project is simultaneously positioned as both a world-ending problem, and the solution to that same problem (which would not exist without the efforts of technofascists) for a select, enlightened few.

The death cult of technofascism is demonstrated with perfect clarity by the closely-related ideologies surrounding Large Language Models (LLMs), Artificial General Intelligence (AGI), and the bundle of ideas known as TESCREAL (Transhumanism, Extropianism, Singulartarianism, Cosmism, Rationalism, Effective Altruism, and Longtermism)(5).

We can derive examples of this death cult from the examples given in the previous section. In the concept of the Bitcoin Citadel, cryptocurrencies are idealized as both the cause of the collapse and as the in-group’s source of power after that collapse(6). The TESCREAL belief that Artificial General Intelligence (AGI) will end the world unless it is “aligned with humanity” by members of the death cult, who handle the AGI with the proper religious fervor(11).

While Urbit does not technologically structure itself as a death cult, its community and network is structured to be a highly effective incubator for other death cults(2, 7, 10).

Severance of our relationship with truth and scientific research

Destruction and redefinition of historical records

This can be viewed as a furtherance of technofascism’s goal of destroying our ability to perceive the truth, but it must be called out that technofascist projects have a particular interest in distorting our remembrance of history; to make history effectively mutable in order to cover for technofascism’s failings.

Parasitization of existing terminology

As part of the process of generating false consensus and covering for the many failings of technofascist projects, existing terminology is often taken and repurposed to suit the goals of the fascists.

One obvious example is the popular term crypto, which until relatively recently referred to cryptography, an extremely important branch of mathematics. Cryptocurrency communities have now adopted the term, and have deliberately used the resulting confusion to falsely imply that cryptocurrencies, like cryptography, are an important tool in software architecture.

Weaponization of open source and the commons

One of the distinctive traits that separates ordinary capitalist exploitation from technofascism is the subversion and weaponization of the efforts of the open source community and the development commons.

One notable weapon used by many technofascist projects to achieve absolute control while maintaining the illusion that the work being undertaken is an open source community effort is what I will call forking hostility. This is a concerted effort to make forking the project infeasible, and it takes two forms.

Its technological form is accomplished via network effects; good examples are large cryptocurrency projects like Bitcoin and Ethereum, which cannot practically be forked because any blockchain without majority consensus is highly vulnerable to attacks, and in any case is much less valuable than the larger chain. Urbit maintains technological forking hostility via its aforementioned implementation of neofeudal network resource allocation.

The second form of forking hostility is social; technofascist open source communities are notably for extremely aggressively telling dissenters to “just for it, it’s open source” while just as aggressively punishing anyone attempting a fork with threats, hacking attempts (such as the aforementioned blockchain attacks), ostracization, and other severe social repercussions. These responses are very distinctive in the uniformity of their response, which is rarely seen even among the most toxic of regular open source communities.

Implementation of racist, biased, and prejudiced systems

References

[1] Bender, Emily M. and Hanna, Alex, Ai Causes Real Harm. Let’s Focus on That over the End-of-Humanity Hype, Scientific American, 2023.

[2] Broderick, Ryan, Inside Remilia Corporation, the Anti-Woke Dao behind the Doomed Milady Maker Nft, Fast Company, 2022.

[3] Duesterberg, James, Among the Reality Entrepreneurs, The Point Magazine, 2022.

[4] Eco, Umberto, Ur-Fascism, The Anarchist Library, 1995.

[5] Gebru, Timnit and Torres, Emile, Satml 2023 - Timnit Gebru - Eugenics and the Promise of Utopia through Agi, 2023.

[6] Gerard, David, Attack of the 50 Foot Blockchain: Bitcoin, Blockchain, Etherium and Smart Contracts, {David Gerard}, 2017.

[7] Gottsegen, Will, Everything You Always Wanted to Know about Miladys but Were Afraid to Ask, 2022.

[8] Munster, Decrypt / Ben, The Bizarre Rise of the ’Bitcoin Citadel’, Decrypt, 2021.

[9] , Scope Creep, Wikipedia, 2023.

[10] , How to Start a Secret Society, 2022.

[11] Torres, Emile P., The Acronym behind Our Wildest Ai Dreams and Nightmares, Truthdig, 2023.

[12] Yarvin, Curtis, 3-Intro.Txt, GitHub, 2010.

  • froztbyte@awful.systems
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    @self quite like what I’ve read so far, questions and thoughts follow

    1. the layout of this seems like it’s meant to be a standalone article/post, rather than as a response of sorts (which is fine ofc). I could imagine something of the latter being useful, do you foresee this having a response sibling-post to go with it? or would that be a diy thing for others to write while referencing this?

    2. along the topic of the weaponisation of open source, there’s something that’s been irking me for a while and that I’ve been short on spoons to write it (feel free to run with it if it’s any good): many, many, many of these projects feature the most absolutely ridiculous naïve-fragile designs, under the guise of “don’t worry, just ship it, you can just iterate”. there’s rarely any depth given to thinking about “but what about …” conditions, and always it’s shunted off into the “oh but if we’re actually having those problems, we’re already successful” kind of considerations/discussions. this last bit, of course, is bonkers because lots of The Bros want you to commit to their chosen thing ritenao, but seem to be incapable of even exploring that space at all (or, if/when they do, you get megawordvomit medium articles with simple industrial realisations in them)

    3. [nit] the footnote ordering appears to be funky, I’m guessing that’s a braindump/writing-time ordering issues?

    • self@awful.systemsOPM
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      thank you! I really appreciate the feedback, and it’s making me want to start on the second draft of this much sooner than expected.

      the layout of this seems like it’s meant to be a standalone article/post, rather than as a response of sorts (which is fine ofc). I could imagine something of the latter being useful, do you foresee this having a response sibling-post to go with it?

      this is the first draft of a standalone post, but I also want it to be the prelude to an eventual series of posts on technofascism. a response post could absolutely be part of that series if there’s a desire for it.

      along the topic of the weaponisation of open source, there’s something that’s been irking me for a while and that I’ve been short on spoons to write it (feel free to run with it if it’s any good): many, many, many of these projects feature the most absolutely ridiculous naïve-fragile designs, under the guise of “don’t worry, just ship it, you can just iterate”.

      absolutely! this ties in with more than one techfash mechanism: alongside the weaponization of open source, this can also be seen as a reflection of the techfash disdain for good/successful engineering. in this case, it’s an amplification of a tendency that the technofascists took from venture capital and startup culture: the idea that shipping product and “changing the world” right now is more important than good engineering. I’d say the distinguishing line between the VC version of this tendency and its techfash form is that startups do at least attempt the cycle of iteration, while techfash projects only use it as a cover for their actual goals.

      [nit] the footnote ordering appears to be funky, I’m guessing that’s a braindump/writing-time ordering issues?

      this should hopefully get better, but it’s from a combination of two things: a complete lack of experience with Zotero (which I should have started using much sooner) and an obsession with Emacs, leading me to fight way too much with org-mode’s citation system. there’s very likely a better way to export citations (and I’ll likely change citation formats either way once this post reaches a more finalized state), but it’ll take a bit more experience on my end to figure out how to make it work

      • froztbyte@awful.systems
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        absolutely! this ties in with more than one techfash mechanism: alongside the weaponization of open source, this can also be seen as a reflection of the techfash disdain for good/successful engineering. in this case, it’s an amplification of a tendency that the technofascists took from venture capital and startup culture: the idea that shipping product and “changing the world” right now is more important than good engineering. I’d say the distinguishing line between the VC version of this tendency and its techfash form is that startups do at least attempt the cycle of iteration, while techfash projects only use it as a cover for their actual goals.

        it also feels like the “builder” bullshit dovetails along the same angle - the VC lot have liked to pitch the false “there’s builders, and everyone else” dichotomy for a while, and then the coiner etc grifters took that and ran with it in a similar perversion as what you note here

        another thought I had (which didn’t make it through the fog last night): another nasty dimension of the way they push shit is the misappropriation of “the community” - beyond the usual the bad-faith reasons along which they “build community” (which I believe others have written about before), there’s also an intentional expectation of offloading the “later” of the work on “the community”, and there’s been a fairly severe attempt at normalising this

        this should hopefully get better, but it’s from a combination of two things: a complete lack of experience with Zotero (which I should have started using much sooner) and an obsession with Emacs, leading me to fight way too much with org-mode’s citation system. there’s very likely a better way to export citations (and I’ll likely change citation formats either way once this post reaches a more finalized state), but it’ll take a bit more experience on my end to figure out how to make it work

        mood:

        spoiler

        in this picture

        • self@awful.systemsOPM
          link
          fedilink
          arrow-up
          5
          ·
          1 year ago

          another nasty dimension of the way they push shit is the misappropriation of “the community”

          I will write more on this in the long-form reply to @[email protected]’s feedback, but what’s interesting is misappropriation and weaponization of the commons is something fascism has been doing essentially from the start. this is why many fascists steal terminology from socialism, falsely claim to have socialist goals, and even occasionally outright call themselves socialists or communists if it’s useful to advance their real goals. point 13 of Ur-Fascism is relevant here (and even calls out Internet populism as a fascist tool, way back in 1995 [1]), but generally, this kind of subversion of the commons is a very old and extremely effective pathway for fascism.

          [1] there are a lot of incredibly prescient authors who called out the mechanisms of technofascism under other names as early as the 90s, before the dot com bubble burst. @[email protected] has been making some very good reading recommendations in that area, from authors whose work deserves much more attention now that the problems they pointed out are worse and everywhere.

          mood:

          hahaha, it’s like my programmer habits and my desire to write are constantly fighting each other