Update: Actually, I just changed my user-agent from one that advertises my browser as emacs-w3m to one that advertises itself as a common Mozilla/Chrome/Safari browser and I no longer get redirected and can read the original article just fine.
I tried and this just worked for me:
ftp -o wp.html http://www.washingtonpost.com/science ...
That fails and automatically switches to https and then fetches the article. The formatting isn't ideal but the article text is readable.So many ways to skin a cat, so to speak!
Second time I have heard about this ... which is confusing because I use lynx on a regular basis on OpenBSD.
tl;dr: 1.1.1.1 doesn't pass along any client IP information for privacy reasons and archive.is won't return a good DNS response without it
Passing just the subnet is not revealing your IP. IP reveal would have much bigger privacy implications.
Cloudflare's conflict of interest is what Archive.is is really protesting. More here: https://webapps.stackexchange.com/questions/135222/why-does-...