• Re: archive.org "read-only" . . .

    From Kerr-Mudd, John@21:1/5 to noreply@mixmin.net on Mon Oct 14 20:32:30 2024
    On Mon, 14 Oct 2024 20:21:33 +0100
    D <noreply@mixmin.net> wrote:


    (using Tor Browser 13.5.7)
    https://duckduckgo.com/?q=archive.org+read+only

    been testing known archives and it works normally . . .


    Hoo, and indeed, rah.

    --
    Bah, and indeed Humbug.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From D@21:1/5 to All on Mon Oct 14 20:21:33 2024
    (using Tor Browser 13.5.7)
    https://duckduckgo.com/?q=archive.org+read+only

    been testing known archives and it works normally . . .

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Computer Nerd Kev@21:1/5 to noreply@mixmin.net on Tue Oct 15 06:59:52 2024
    D <noreply@mixmin.net> wrote:

    (using Tor Browser 13.5.7)
    https://duckduckgo.com/?q=archive.org+read+only

    been testing known archives and it works normally . . .

    Ah, it wasn't just me then. I've been suffering a lot without the
    Wayback Machine. I assumed that they'd DDoS'ed themselves by
    agreeing have Google link to them instead of their now-dead cache
    in web search results.

    Oh, I just tried to load the website I was looking for the other
    day and got "504 Gateway Time-out", but at least the URL reveals
    that business really did have a website once. Anyway I found their
    email address and actually got in contact with them already through
    that, even though it seems their website was last captured in 2017.

    The 2016 capture loaded. Doesn't say much anyway, not even their
    email address!

    --
    __ __
    #_ < |\| |< _#

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)