zlacker

>>rabino+(OP)
Remember when Archive.is/today used to send Cloudflare DNS users into an endless captcha loop because the creator had some kind of philosophical disagreement with Cloudflare? Not the first time they’ve done something petty like this.

>>rafram+uV
It wasn't a philosophical disagreement, they needed some geo info from the DNS server to route requests so they could prevent spam and Cloudflare wasn't providing it citing privacy reasons. The admin decided to block Cloudflare rather than deal with the spam.

>>stavro+ln1
Had nothing to do with spam, the argument by archive.today that they needed EDNS client subnet info made no sense, they aren't anycasting with edge servers in every ISP PoP.

>>arcfou+fu2
They use EDNS for regional compliance, not for bandwidth optimization.

>>venteg+Bx2
What specific part of regional compliance actually needs this, and why does no other website seem to need it?

>>joseph+ge4
e.g. currently most media snapshots contain wartime propaganda forbidden at least somewhere.

RT content verboten in Germany, DW content verboten in Russia, not to mention another dozen of hot spots.

"Other websites" are completely inaccessible in certain regions. The Archive has stuff from all of them, so there’s basically no place on Earth where it could work without tricks like the EDNS one.

>>venteg+Hk5
That makes zero sense. You're aware that they get the client's actual IP upon connection?

You're saying they have groups of servers with every possible permutation of censorship that they direct clients to through DNS? Absurd.

>>arcfou+JG5
They always direct clients to a server abroad. The task is exactly opposite to what CDNs do