I can never get past the endless captchas on this site.
https://community.cloudflare.com/t/archive-today-does-not-re...
One affects their DNS resolution of archive.is, GP is talking about Cloudflare's endless captcha portal on that site. Strangely enough, it works for me today, but a few days ago I couldn't get past that obnoxious screen.
I just wish people would stop flocking to Cloudflare and making the internet even shittier than it is.
The thread you’ve linked to isn’t very clear on its own -- it seems like it’s missing a lot of context.
The first reply makes it sound like archive.is is blocking Cloudflare, but it sounded like you meant the opposite.
(And I assume this is all separate from the CAPTCHA thing, as the other reply says)
2023:'public-dns'
However, changing your DNS is the answer to the problem.
You will see I do not have any problem accessing archive.is
The Cloudflare vs. Archive.today is a years old problem, thoroughly discuses on HN:
And for the record; I use Firefox with uBlock-Origin and Steven Black's hosts file on a Debian flavored Linux.
Of course I no longer use Cloudflare DNS
Cloudflare can't point me to their own servers when I access https://archive.today unless my browser confirms that the server it's talking to (the one serving the CAPTCHAs) has archive.today's certificate's private keys.
'"cloudflare" vs "archive.is"' site:news.ycombinator.com
HN Discussion - (210-comments - 2023-08-02) : https://news.ycombinator.com/item?id=36970702
However, All our comments regarding DNS have really derailed this thread. (sorry mods)
This doesn't explain why some would see a huge amount of CAPTCHA served by archive.is or archive.today if they do reach an IP that serves the right TLS certs, but only if they got that IP from 1.1.1.1 instead of getting it from 8.8.8.8 or wherever.