Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
I have never done anything like this before. I have always been a law-abiding citizen, but I decided I needed to stand with my family and do what I can to help stop new coal.
The archive.today captcha loop is their passive-aggressive way of complaining that your DNS provider isn’t using eDNS to send them approximate location information. It’s mostly being hit by firefox users because firefox uses a dns-over-https system which obscures location information by default. You can add exceptions to the DNS and HTTPS settings to get around it.
Ah! I had seen something regarding DNS issues when I did a cursory search. I’m using private relay with safari (lurking via IOS app) so I imagine it’s similar. Thanks for the info!
Or… don’t use an archive service that has a tantrum if it doesn’t have your approximate location… which you should Not be giving away to anyone, really.
Archive org link incase anyone else gets stuck in a captcha loop
The archive.today captcha loop is their passive-aggressive way of complaining that your DNS provider isn’t using eDNS to send them approximate location information. It’s mostly being hit by firefox users because firefox uses a dns-over-https system which obscures location information by default. You can add exceptions to the DNS and HTTPS settings to get around it.
Shit that annoys me
Ah! I had seen something regarding DNS issues when I did a cursory search. I’m using private relay with safari (lurking via IOS app) so I imagine it’s similar. Thanks for the info!
Or… don’t use an archive service that has a tantrum if it doesn’t have your approximate location… which you should Not be giving away to anyone, really.
They do way better at serving content without pop-overs than anybody else though