[user_7832]

Their policies have apparently… changed. They accept donations to not have your website bypassed. Archive.org is much better.

Edit: apparently it is down now.

402: PAYMENT_REQUIRED Code: DEPLOYMENT_DISABLED ID: fra1::8wkv2-1699275385535-39dedae23d6a

[jdiff]

Is it donations they accept or legal threats?

[ProllyInfamous]

Yes.

[i67vw3]

Archive.today never fails compared to Archive.org or various browser extensions

To remove paywalls 12ft<Archive.org<Archive.today is my opinion.

[giancarlostoro]

For some reason all the alternative "archive.XYZXDHWIQHDQ" type of sites always give me a captcha page, and I am never able to proceed. I'm assuming its to do with the cloudflare DNS, well if they don't care to fix it on their end, I don't care to use their service.

[i67vw3]

There is a bit of 'tussle' going on between the two of them for quite a few years as you pointed out.

https://x.com/archiveis/status/1018691421182791680?s=20

https://news.ycombinator.com/item?id=36971650

https://news.ycombinator.com/item?id=19828702

https://news.ycombinator.com/item?id=36971552

[flutas]

IIRC:

It's kind of a "everybody sucks" situation and there's no real winners.

Archive.[whatever] setup a server system to give you access from a country not your own, so that abusers have a harder time of archiving illegal content, then instantly reporting it to get the entire archive taken down. He uses EDNS to do this, but CF doesn't provide EDNS since it's a privacy issue to them.

So archive.[whatever] doesn't work for CF DNS because he doesn't want to risk bad actors being able to take down the archive.

Sensible reasons on both sides, especially for a service like archive.[whatever], and the real losers in this situation are the users.

[PawgerZ]

Copying my previous comment over because I found a fix that works for me:

There's some issue with DNS over HTTPS, so you have to whitelist their sites in your settings, or turn off DNS over HTTPS (which I don't recommend).

To whitelist, on Firefox: Hamburger menu > settings > privacy and security > DNS over HTTPS > Manage exceptions > Add "archive.is", "archive.ph", and "archive.today"

[Brian_K_White]

It has nothing to do with dns-over-https, it has to do with using cloudflare dns at all, over https or plain.

In my case I added override rules in my opnsense router so that archive.is .ph .today .md are all resolved by a different nameserver.

Disabling DOH can appear to fix it only in the happenstance case that the fallback plain dns doesn't end up using cloudflare, or doesn't use it first.

[LargoLasskhyfv]

Why not using this instead? Too slow?

https://mullvad.net/en/help/dns-over-https-and-dns-over-tls/

No issues with any archive-sites.

Aside from not being censored at all, thereby enabling visiting sites which are blocked at DNS-level in some locations, there are several options for adblocking at DNS-level, too. Often eliminating the need for a Proxy or VPN to get access, with optional Adblock as a service.

For free.

It's nice.

[Brian_K_White]

What do you mean why not? The point is just to use anything other than cloudflare for archive.is, and mullvad is not cloudflare, so seems fine, go ahead.

There is no special reason not to use cloudflare dns in general though.

The problem is only between cloudflare and archive.is (and it's aliases) and it's hard to say if either side is wrong, except for the fact that either or both of them could figure out some special exception where they recognize each other's traffic if they cared to. Cloudflare are not censoring archive.is for example, and are not doing anything wrong.

[ryeights]

For those on mobile it was the opposite, since the archive sites only show you the desktop sites

[gnicholas]

Does reader mode work on archive sites?