David Gerard (@[email protected])
circumstances.run
Urbit announced its summer acceleration program. Being made of smarmy edgelords, they called it "u/acc". I mentioned this and someone asked wtf is an Urbit. So!! Urbit is the OS founded by Curtis Yarvin, aka the creator of neoreaction Mencius Moldbug. Urbit is a new paradigm for computation that combines functional programming with what happens when libertarian anarcho-capitalism goes so right-wing reactionary that it openly turns into Hans-Hermann Hoppe’s vision of neo-feudalism. And that sentence needs a Wikipedia article per jargon word. Think "what if networked Lisp machines, but for Nazis." Urbit isn’t useful for anything. The apps don’t work, and the ones that do work bypass the language that the functional programming vision of the system is supposedly based on. I would call Urbit "TempleOS on the blockchain", but that makes it sound too interesting. Urbit outdoes bitcoin for the degree to which it combines "interesting" in the sense of "what the hell even is this" and "I'm not even mad, that's amazing" with utter unfeasibility and utter uselessness. This is what gives Urbit what little life it has: it's technically technically-interesting, but utterly unusable. Other functional programmers think it's trash. The only FPs who take it seriously are also techfash. So Urbit has no technical merits to succeed on, and only its political cult. So it leans *hard* into that cult. Urbit's only function is as an identifier to fellow fash. Which it's serving admirably. Only one kind of person has an Urbit. If you see a string of the format "~abcdef-ghijkl" in someone's bio (tilde, six letters, hyphen, six letters), they're that kind of person. If you really want to understand "yes, but *why* Urbit?" "why the *fuck* Urbit?" then the answer is still Elizabeth Sandifer's book Neoreaction a Basilisk. I believe the approved method is to libgen it and *also* buy the paperback. As we all know, the use case for social media is to get laid. So I wonder if there's pent-up neoreactionary passion just waiting to be unleashed on Urbit. I expect the incel forums there are a delight. ==== EDIT: "e/acc" is short for "effective accelerationism", a condensed version of Nick Land's bad "Dark Enlightenment" ideas. This became trendy with neoreactionaries, who tagged themselves with "e/acc". It's a reasonably reliable way of spotting incredibly blockable little shits. It's dumb enough there's a KnowYourMeme on it: https://knowyourmeme.com/memes/cultures/eacc-effective-accelerationism so Urbit is riffing on the meme.
  • self@awful.systemsMEnglish
    1·
    1 year ago

    I decided to head the acasualrobotgod off at the pass and torture myself by reading through the early Urbit spec in full (whose content is completely different from the one @[email protected] posted), and I found something interesting; the info I gave above about Urbit taking ideas from Nix isn’t quite accurate. the reality is much worse.

    so yarvin’s specs are meandering as fuck of course, but eventually they get to some kind of point. in short, Urbit’s main computational function consists of two other functions.

    • urbit-infer knows how to pull code from the network, cryptographically verify its integrity, and transform (build) it. this is Nix’s fetchurl and half of Nix’s derivation function.
    • urbit-render takes the output of urbit-infer and stores it in a unique path in Urbit’s pathspace. this is the other half of derivation.
    • the Urbit pathspace is a set of paths on a storage device with the invariant that every path must uniquely represent an output of urbit-infer, and that the existence of a path guarantees that its contents are the output of urbit-render for that path’s instance of urbit-infer. this is just Nix’s core data structure, the Nix store, copied wholesale into Urbit but with a much stupider uniqueness algorithm

    now note that Nix is actually a lot older than I indicated before. it was first released in 2003, and Eelco Dolstra’s first paper on it was published in 2004, 6 years before Yarvin’s first posts about Urbit. that 2004 paper featured details on derivation, fetchurl, and the Nix store, all of which exist almost unchanged in modern Nix

    a lot of the differences between Urbit and Nix (like pathspace forks) seem to be attempts to work around implementing the trickier parts of the Nix evaluation model

    given the big similarities in functionality and structure between the Urbit computational function and Nix’s core functions and data structure, the wide span of time during which Yarvin could have read the Nix paper (and Dolstra published about Nix several more times between 2004 and 2010), and Nix’s obscurity until around 2015, I’m willing to upgrade my suspicion to an accusation:

    Urbit’s core functionality is a shitty, plagiarized version of Nix, but intentionally crippled to keep Yarvin in control

    this has got to be my last Urbit deep dive for a while, but I figured it couldn’t hurt to write up some notes here in case Urbit starts marketing hard again