Cloudflare and archive.is apparently don’t agree on how to implement DNS, so if you’re using 1.1.1.1 (like myself) you’ll get an error. This is the explanation I had seen elsewhere and I was like “Yep, that applies to me.” (I assume it’s happening with all variations of the archive site including archive.ph)
I found this[1] by searching around HackerNews, seems like a relatively decent overview of what is happening. Kinda paints the archive team in a not-so-great light, in respect to privacy considerations, in my opinion.
8.8.8.8 is Google’s DNS, which is not very privacy respecting of which sites you access. 1.1.1.1 is Cloudflare’s and it is a lot more privacy-respecting while still being imperfect. However their track record in the privacy/security community is currently quite good, so it’s up to you if those imperfections are a problem or not.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !politics@beehaw.org
In-depth political discussion from around the world; if it’s a political happening, you can post it here.
Guidelines for submissions:
Where possible, post the original source of information.
If there is a paywall, you can use alternative sources or provide an archive.today, 12ft.io, etc. link in the body.
Do not editorialize titles. Preserve the original title when possible; edits for clarity are fine.
Do not post ragebait or shock stories. These will be removed.
Do not post tabloid or blogspam stories. These will be removed.
Social media should be a source of last resort.
These guidelines will be enforced on a know-it-when-I-see-it basis.
Cloudflare and archive.is apparently don’t agree on how to implement DNS, so if you’re using 1.1.1.1 (like myself) you’ll get an error. This is the explanation I had seen elsewhere and I was like “Yep, that applies to me.” (I assume it’s happening with all variations of the archive site including archive.ph)
I found this[1] by searching around HackerNews, seems like a relatively decent overview of what is happening. Kinda paints the archive team in a not-so-great light, in respect to privacy considerations, in my opinion.
https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ ↩︎
Ahh, interesting. I do indeed use 1.1.1.1, in part because of DNS-over-TLS that it supports. Thanks for the link.
Is 1.1.1.1 like open source DNS? I used 8.8.8.8 (4.4.8.8?) for a long time when ISPs sometimes we’re flaky, any pointers for what to use nowadays?
It’s not open source, it’s DNS run by Cloudflare. It’s a privacy-oriented DNS service. You can read about it here: https://blog.cloudflare.com/announcing-1111/
8.8.8.8 is Google’s DNS, which is not very privacy respecting of which sites you access. 1.1.1.1 is Cloudflare’s and it is a lot more privacy-respecting while still being imperfect. However their track record in the privacy/security community is currently quite good, so it’s up to you if those imperfections are a problem or not.