“This step is necessary to prove I’m not a bot,” wrote the bot as it passed an anti-AI screening step.

  • justOnePersistentKbinPlease@fedia.io
    link
    fedilink
    arrow-up
    113
    ·
    2 months ago

    Makes sense.

    1. Google’s “anti bot” verification has long been considered woefully inadequate.
    2. It works largely by tracking how long the user takes to click on it.
    3. LLMs are inherently fuzzy and for a bot, incredibly slow.
          • Passerby6497@lemmy.world
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            1 month ago

            You have to have a Cloudflare captcha solver for some of the *arr stack to work with certain indexers or something, idk. When my old *arr stack died and had to be rebuilt I ran into that problem, and after a short investigation, I promptly said fuck it and learned usenet. So happy that I did.

            • Billygoat@catata.fish
              link
              fedilink
              English
              arrow-up
              2
              ·
              1 month ago

              I think the confusion comes from people misunderstanding that cloud flare isn’t being set up in front of the arr stack, Instead, what people are talking about is flaresolverr, an application that helps services like jackett bypass cloudflares verification.

        • Midnight_Oil@piefed.social
          link
          fedilink
          English
          arrow-up
          4
          ·
          2 months ago

          From the screenshot in the article, the bot is bypassing Cloudflare’s Turnstile which is not just tracking hits.

          I work in bot detection. You and anyone else reading this should understand that, behind the scenes, proof-of-work, proof-of-space, and other tests are being run to verify if the device is what it says it is. Typically, a bot is run with a tool like Playwright or Puppeteer. These frameworks are detectable with the right tests. Bots will also attempt to spoof another device’s fingerprints to blend in. These changes are also detectable if you know what to test for.

          We implement tools like Turnstile and other CAPTCHAless CAPTCHA because bots are pretty good at passing CAPTCHA while humans, rightfully, hate verifying they they’re human. Humans also struggle at passing CAPTCHA.

          The general population has zero idea the massive volume of bot traffic that is being generated right now. These tools are implemented for a reason. So the fact that a bot just breezes past this test is a problem for us all.

          Definitely not “same shit different pile”, friend.

          • justOnePersistentKbinPlease@fedia.io
            link
            fedilink
            arrow-up
            4
            ·
            1 month ago

            Thanks for the write up, but I was blocked from logging in on a cloudflare website because I opened too many windows once and their tracking cookie flagged that browser as a bot.

            Meanwhile the bot I built to track mod updates to my modlist for Rimworld and Mw5 on nexus? Never ran into any issues.

            So when I refer to Cloudflare’s bot detection as shit, that is a highly personal and professional opinion.

          • chameleon@fedia.io
            link
            fedilink
            arrow-up
            1
            ·
            1 month ago

            The modern breed of CAPTCHAs is mostly only trying to verify that it’s a full-fat browser. undetected-chromedriver, camoufox, pydoll, patchright and a million other libraries/tools exist. Nothing’s perfect and it’s a cat & mouse game, but this single incident is a sample size of one as well.