home.social

#y2038 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #y2038, aggregated by home.social.

  1. @arcaneoverflow @thomasfuchs It is 2037, the distant grim future of programming. The oceans have been boiled by #slopfondlers in order to, well, fondle slop. The cities, animals, stars, everything else really have also been boiled. You are right to call me out on this #error but there you have it. All code on the Internet is #slop. LLM #training has ground to a halt: any new model is worse than all previous ones, combined.
    Programmers live alone, in caves. Nobody wants to live with them. Their communication networks all collapsed after the great AI-assisted revolution tried to unify #Fediverse and #ATProto. It failed, but auto-upgrades enforced at the #hardware level make reintegration impossible.
    Suddenly a #ITU session recalls - the #y2038 problem is looming! But: it is impossible to communicate with programmers, and — surprising nobody — no model can produce code. But in the ashes of a dying world lurks a #diamond: #INTERCAL! INTERCAL code has never been touched by LLMs. Devoid of a multi-quadrillion dollar #valuation, the codebase is entirely slop-free. There are even binaries for a working #CIntercal implementation!

    This is the future: train an LLM on all INTERCAL code, free of previous LLM influence. A brave group of rebels strips GPUs from fallen datacentre #satellites - remains of a dumb investment humanity made nearly 15 years ago, but whose remnants are still falling back the #earth. A @ed1conf member manages to code a list of #curl commands to download all INTERCAL programs. It might not work, but at least #humanity will not go down without a fight.

    Unfortunately, it fails. 2038 arrives, #int32_t wraps around, and humanity is no more.

  2. @arcaneoverflow @thomasfuchs In the grim future of LLM training data (the year 2037), the Internet is a desolate wasteland. The oceans, the night sky, and all the volcanoes have been boiled away by #slopfondlers fondling their slop. Corporations have wasted quadrillions of dollars and destroyed all code. Programmers have been cast out of society and live online in isolated #fediverse servers. An LLM updated #RFC9421 incorrectly, some servers auto-updated incorrectly, and all communications are down.
    Suddenly someone remembers the #y2038 apocalypse! But programming is no longer possible: all LLMs have been #trained_on_trash. Humanity's only chance is to train a new LLM, on non-trash code. But where to find such code? #INTERCAL is the only possible way. Sextillions of dollars are spent training a top-tier LLM model on INTERCAL alone.
    It fails. Humanity is gone.

  3. Ein bemerkenswerter Artikel in der Schweizer Zeitung La Liberté über das Jahr-2038-Problem:
    laliberte.ch/articles/monde/le
    Besonders erfreulich: Er erwähnt XSTP.epoch, das im Juni von ITU-T SG17 in Genf verabschiedet wurde.
    Und im Acknowledgement wird auch unsere Arbeit aus der FIRST Time SIG und der Epochalypse-Community gewürdigt. Ein kleiner, aber schöner Meilenstein.
    #Y2K38 #XSTPepoch #y2038 #DasJahr2038Problem

  4. Vor 20 Jahren trat der erste bekannte Y2K38-Bug in Produktion auf.

    Beim Open-Source-Webserver AOLserver führte „jetzt + 1 Milliarde Sekunden“ erstmals über die 32-Bit-Zeitgrenze hinaus. Verbindungen liefen sofort ab, Timer kippten, Scheduler blockierten.

    Das Jahr-2038-Problem war damit nicht mehr theoretisch.

    Und 20 Jahre später ist es noch immer nicht gelöst.

    y2k38.ch/aolserver-2038-proble

    Edit: Fixed Link

    #Y2K38 #Y2038 #TechHistory

  5. Kleine Umfrage zum Jahr-2038-Problem👇

    Was meint ihr, wie werden die Auswirkungen sein?

    Teilt die Umfrage gern weiter, bin gespannt auf eure Einschätzungen 🙂

    Begründungen gerne in den Kommentaren.

    #y2k38 #y2038 #DasJahr2038Problem

  6. Y2K38 kommt. Milliarden Systeme sind betroffen.

    Open Source wird kritisiert – dabei entstehen die Lösungen oft genau dort.

    Das Problem ist nicht der Code.
    Das Problem ist, wie wir damit umgehen.

    👉 Wer zahlt am Ende die Rechnung?

    y2k38.ch/y2k38-open-source-sue

    #y2k38 #opensource #year2038 #y2038