• @whaleross@lemmy.world
    link
    fedilink
    621 year ago

    My guess is that at some point some poor web dev or web admin screwed up big time and with a heart rate nearing the colibri fluttered in panic above their laptop in attempts to restore the site, finding great relief that there was a snapshot in the archives and did not have enough presence to fix all the links to get it back online asap.

    • @GoosLife@lemmy.world
      link
      fedilink
      261 year ago

      …and he didn’t think to download the files and host them properly instead? Surely this must be some kind of fallback or the user is actually browsing the internet archive, no?

      • @bus_factor@lemmy.world
        link
        fedilink
        371 year ago

        They’re suggesting that they copied the HTML file, but that the archived one had modified references pointing to archive.org, which they did not notice and therefore didn’t change. So now the file fetches resources from the wrong place.

      • @kautau@lemmy.world
        link
        fedilink
        81 year ago

        Probably the production version of JS broke something on that page, getting the infrastructure team involved in “we now need to host multiple JS versions” was scary, especially if they fucked something up, so easier to modify the code on that page to point to the archive.org snapshot of the JS