• DigitalPaperTrail@kbin.social
    link
    fedilink
    arrow-up
    55
    ·
    edit-2
    1 year ago

    I’m convinced the person that put it together has never touched a faster-paced mouse+keyboard game in their life, because clicking all the correct squares too fast also causes the test to fail

    • jmcs@discuss.tchncs.de
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      That’s what a bot would say /s

      But you’re right, the UX sucks, and there are other ways to detect and limit bots that don’t impact legitimate users as much - but Google needs to train their AI, and developers need to cargo cult stuff.

    • nottheengineer@feddit.de
      link
      fedilink
      arrow-up
      7
      ·
      1 year ago

      These things feel like they are made by microsoft. You click somewhere, wait 3-10 seconds and then you can click again.

      • Droechai@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Just use a click delay program between press and input, maybe with a physical on/off switch on a dedicated keyboard next to the mouse together with other necessary keys (like the one button switch between EN and SE layouts or the Memory Cache Dump Key)

    • Tetsuo@jlai.lu
      link
      fedilink
      arrow-up
      0
      arrow-down
      7
      ·
      1 year ago

      A bot trying to solve the captcha would be very fast so it makes sense that they block fast solvers.