4 ms·
Iirc, it has to due with their infrastructure and DNS queries. The short of it, as I understand it, is they try connect you to instances far away from your geo
by DistractionRect 3y ago
Iirc, it has to due with their infrastructure and DNS queries. The short of it, as I understand it, is they try connect you to instances far away from your geo location because it gives them a longer time to process legal takedown requests. So some DNS do something that conflicts with this, and so they serve up the infinite captcha instead. I have this problem if I use cloudflare for domain name resolution, but it goes away if I use something else (like Google, my ISP, etc).
Edit: found it, cloudflare truncates edns, which is why archive sandbags requests that are boot strapped with a cloudflare dns lookup:
https://news.ycombinator.com/item?id=36970702 https://news.ycombinator.com/item?id=36970702
- godelski 3y agoI think it is affecting more than just cloudflare users. Also, we should be, imo, pointing fingers at archive and not cloudflare because they strip the edns for privacy reasons. Archive's response is just that they don't store that, which isn't a great excuse. And I think this gets worse with encrypted DNS, which should be fucking standard these days. My reading of it felt like the classic dev move of "that's not my problem, that's other people's problem" (https://imgflip.com/i/8559hq https://imgflip.com/i/8559hq)
- WarOnPrivacy 3y ago> I think it is affecting more than just cloudflare users. It is absolutely hitting more the Cloudflare users. It's not that old edns issue (tho might it be tangentially related).
- godelski 3y agoYeah I think people think it is just cloudflare and so they get blamed when it is archive pulling some fuckery. I mean I get that it's a small team (or just one dude?) but still it is annoying when devs are like "rtfm" (in spirit) but there actually isn't a fm to read... It's why I don't open issues on GitHub... P.S got a typo there? the -> than?