Archive Today has an endless ReCAPTCHA loop presently | Hacker News Reader

Archive Today has an endless ReCAPTCHA loop presently

archive.today

1 pointdredmorbius7 comments

Interesting ...

Using Cloudflare (1.1.1.1) vs. Google (8.8.8.8) I get different IP resolution:

  for u in archive.ph archive.is archive.li archive.vn archive.fo archive.md;
  do
      echo ">>> ${u} <<<";
      host -t A $u 1.1.1.1;
      host -t A $u 8.8.8.8;
  done

Results:

  >>> archive.ph <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.ph has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.ph has address 23.137.248.133
  >>> archive.is <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.is has address 198.23.187.186
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.is has address 23.137.248.133
  >>> archive.li <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.li has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.li has address 23.137.248.133
  >>> archive.vn <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.vn has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.vn has address 23.137.248.133
  >>> archive.fo <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.fo has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.fo has address 23.137.248.133
  >>> archive.md <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.md has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.md has address 23.137.248.133

Cloudflare: Fix your shit.

Amusingly, I'm getting a stuck "checking connection" when trying to connect to Cloudflare's own corporate website:

<https://cloudflare.net/governance/board-of-directors/person-...>

If anyone happens to have Matthew Prince's direct email, could you ping him on this thread? Cloudflare's own support process is broken and I find no email contacts.

Thanks.

I'm among several HN members who're experiencing an endless ReCAPTCHA loop when attempting to access Archive Today (<https://archive.today> a/k/a AT) or any of its various domain aliases:

- <https://archive.ph>

- <https://archive.is>

- <https://archive.li>

- <https://archive.vn>

- <https://archive.fo>

- <https://archive.md>

All resolve to 23.137.248.133 for me.

This has been noted in comments: <https://news.ycombinator.com/item?id=37136514> <https://news.ycombinator.com/item?id=37132089> <https://news.ycombinator.com/item?id=37105936>

As well as an earlier HN story submission: <https://news.ycombinator.com/item?id=37077049>

As a practical upshot, as AT is the principle viable workaround for paywalled articles on HN, which means that HN is now left without a reliable option for such submissions. This becomes a policy issue for HN itself.

There's https://ghostarchive.org and https://12ft.io

12ft.io has been pretty unrewarding for me.

First I've heard of Ghost Archive though, thanks!

Looking more at Ghost Archive:

- There's no DDG bang search as yet.

- I'm not sure there's a submission URL format, though I need to look at how the site operates.

Both of those would be quite useful as my usual archival methods run through DDG (!wayback and !ais, respectively).

Though again, appreciate your mentioning it.

I've heard back from AT's webmaster who writes in part "use of the archive by Hacker News regulars for piracy is problematic" and that it's "gone too far".

Which was not quite what I'd expected.

Implications for HN's policies and practices regarding paywalls are large.

Reply on news.ycombinator.com