3 ms·

For anyone else stuck in a Cloudflare CAPTCHA loop with the archive.today link, you can use archive.vn instead which seems to work: https://archive.vn/HVL3N ht

For anyone else stuck in a Cloudflare CAPTCHA loop with the archive.today link, you can use archive.vn instead which seems to work: https://archive.vn/HVL3N https://archive.vn/HVL3N

herpderperator 3y ago
Unfortunately it's the same issue even with that. I wonder why this is happening. It's very frustrating.
- justinclift 3y ago
  Someone mentioned a few days ago that it happens when using Cloudflare's DNS, though I'm not and it's happening to me now today. Um, maybe try archive.md (aka https://archive.md/HVL3N https://archive.md/HVL3N) and see if that works? I only know of archive.today/vn/md though. There may be others, but I just don't know them.
- nicbou 3y ago
  Turn off DNS over Cloudflare and it works fine
  - justinclift 3y ago
    It's happening to me (only for archive.today), and I'm not using Cloudflare's DNS.
notpushkin 3y ago
It's not even Cloudflare, just made to look like it. reCAPTCHA widget is a dead giveaway, real Cloudflare pages use their own implementation.
- cdchn 3y ago
  Oh. That's kind of weird. Why/who would ape Cloudflare for their detect-a-bot interstitial?
  - notpushkin 3y ago
    I've only seen it on archive.today (& Co.) so I suspect it's an in-house solution. As for why, perhaps it's just because people are already familiar with the Cloudflare one, and they don't want to startle people with a new one? Not sure, but it's my best guess here. Edit: oh, I think I've figured out the why! From the JS comments, I think it's used to get around captchas on archived sites (well, at least LinkedIn) sometimes: var widgetId = grecaptcha.render('g-recaptcha', { 'sitekey': '6LeQbtsSAAAAAHevV56qhVr_0JhQI7N-zTPoOoWJ', // my //'sitekey': '6Lc7CQMTAAAAAIL84V_tPRYEWZtljsJQJZ5jSijw', // linkedin's 'callback': function(response) { // [...snip]
    - cdchn 3y ago
      Interesting. Why would they present it to the user? Are they presenting captchas to sites they're trying to scrape to their users?
      - notpushkin 3y ago
        Yeah, I think it's just a cheap way to get around anti-scraping captchas. The alternative would be to use an anti-captcha service that outsources captcha solving to people in low-wage countries, but that's probably a bit expensive given archive.today's scale.
g-b-r 3y ago
For some reason this works for me

For anyone else stuck in a Cloudflare CAPTCHA loop with the archive.today link, you can use archive.vn instead which seems to work: https://archive.vn/HVL3N https://archive.vn/HVL3N

herpderperator 3y ago

Unfortunately it's the same issue even with that. I wonder why this is happening. It's very frustrating.

justinclift 3y ago
Someone mentioned a few days ago that it happens when using Cloudflare's DNS, though I'm not and it's happening to me now today. Um, maybe try archive.md (aka https://archive.md/HVL3N https://archive.md/HVL3N) and see if that works? I only know of archive.today/vn/md though. There may be others, but I just don't know them.
nicbou 3y ago
Turn off DNS over Cloudflare and it works fine
- justinclift 3y ago
  It's happening to me (only for archive.today), and I'm not using Cloudflare's DNS.

notpushkin 3y ago

It's not even Cloudflare, just made to look like it. reCAPTCHA widget is a dead giveaway, real Cloudflare pages use their own implementation.

cdchn 3y ago
Oh. That's kind of weird. Why/who would ape Cloudflare for their detect-a-bot interstitial?
- notpushkin 3y ago
  I've only seen it on archive.today (& Co.) so I suspect it's an in-house solution. As for why, perhaps it's just because people are already familiar with the Cloudflare one, and they don't want to startle people with a new one? Not sure, but it's my best guess here. Edit: oh, I think I've figured out the why! From the JS comments, I think it's used to get around captchas on archived sites (well, at least LinkedIn) sometimes: var widgetId = grecaptcha.render('g-recaptcha', { 'sitekey': '6LeQbtsSAAAAAHevV56qhVr_0JhQI7N-zTPoOoWJ', // my //'sitekey': '6Lc7CQMTAAAAAIL84V_tPRYEWZtljsJQJZ5jSijw', // linkedin's 'callback': function(response) { // [...snip]
  - cdchn 3y ago
    Interesting. Why would they present it to the user? Are they presenting captchas to sites they're trying to scrape to their users?
    - notpushkin 3y ago
      Yeah, I think it's just a cheap way to get around anti-scraping captchas. The alternative would be to use an anti-captcha service that outsources captcha solving to people in low-wage countries, but that's probably a bit expensive given archive.today's scale.

g-b-r 3y ago

For some reason this works for me