Guardian is not behind a paywall?

Here in the UK, you have to either pay a subscription fee or accept ALL of their tracking cookies in order to read their articles.

I know a lot of people like to dump on Firefox, but a number of paywalls, including the Guardian one, completely disappear when you use it. For those that don't, some of them disappear if you use reader mode.

And archive.is joins their users into botnets

I’ll take the cookies

got any reference for that claim?

It has been discussed on HN pretty frequently since it started happening: https://www.tomshardware.com/software/search-engines/archive...

Wikipedia has deprecated them as a result

Or just toggle JS on their site mate

Isn't that the choice people on hn claim to want to have? Let me pay for journalism and not be tracked please.

You may be surprised to learn that there is more than one person on HN, and also that among the group of people made up of more than one person, some of them have different opinions than others.

there are a lot of sites that do that, especially in germany. and it annoys me to no end because i believe it is actually illegal. at least that's how i understand it. i might be wrong but i believe that tracking cookies must always be optional, paid or not.

This does not work for me.

It's a loop of captcha which never ends

This may be a DNS issue. I had the same problem with NextDNS. After switching my DNS servers to Cloud Flare DNS (1.1.1.1, 1.0.0.1), it works fine.

Switching to Cloudflare DNS solves archive.today problems? That's strange. archive.today is known for having problems with Cloudflare DNS[1]. Switching to Google DNS should solve it. (This isn't because of a bug in Cloudflare DNS, but rather that archive.today dislikes that Cloudflare DNS doesn't support EDNS.)

Disclosure: I work at Google, but not on the DNS team.

[1] https://news.ycombinator.com/item?id=39925822

It’s not. They’ve blocked some countries entirely.

Yeah here in Finland the archive site seems to come and go on a monthly basis.

It's always DNS!

When this happens to me, it's either because I'm connected to a VPN, or I'm using Cloudflare's public DNS server.

Archive blocks VPNs. If you're on one, that could be why.

I've also found that archive.ph is significantly less accessible than archive.is despite hosting the same content. Pausing my VPN for a few minutes and then changing the .ph to .is fixed a similar captcha loop for me, though I still did need to solve a captcha for it.

I was having this problem earlier with different URLs I was searching for but the link above actually worked for me.

are you using a VPN? that happens often to me. might be a combo of that and ublock origin. I'm guessing archive gets a ton of attacks from VPN so they probably just have rules to captcha any VPN address. I have a local proxy on rpi setup and then a container in firefox that lets me use that to quickly swap to a proxy that uses my real IP. very handy for shit like this.

Try this: https://wapo.st/4qqatnA

Yeah never use Cloudflare DNS. They refuse to fix this issue. Use quad9 or Google DNS.

You have some extension issues going on, maybe. Seems to work fine in FF and chrome.

Anecdata: When it happens to me, disabling the VPN helps.

I bet all the downvoting helped with that.