Re:Show HN: Blast – Fast, multi-threaded serving engine for ...
by ATechGuy on Friday May 02, 2025 @05:20PM
(#43874709)
Can browser-use be blocked using Anubis or other anti-bot measures?
Re:Show HN: Blast – Fast, multi-threaded serving engine for ...
by razemio on Saturday May 03, 2025 @07:38AM
(#43878395)
I think these kind of requests can not be blocked. It is like asking if Claude computer control can be blocked from visiting websites. It is not detectable.
You could ofc display captchas which are difficult to solve for an AI.
Re:Show HN: Blast – Fast, multi-threaded serving engine for ...
by diggan on Saturday May 03, 2025 @07:55AM
(#43878476)
As mentioned, browser-use doesn't seem "out of this world" hard to fingerprint since all instances would be using the exact same settings.
Re:Show HN: Blast – Fast, multi-threaded serving engine for ...
by ZeroTalent on Saturday May 03, 2025 @12:14PM
(#43880018)
Browser-use just switched to patchright https://github.com/Kaliiiiiiiiii-Vinyzu/patchright which is an “undetectable” version of Playwright and can rotate/randomize fingerprints. Another extension uses residential proxies and real fingerprints of real people.
Re:Show HN: Blast – Fast, multi-threaded serving engine for ...
by ATechGuy on Saturday May 03, 2025 @12:27PM
(#43880129)
Sorry if I'm missing something, but why can't Anubis not detect/block such AI agents? Is it because they use headful browsers?
Re:Show HN: Blast – Fast, multi-threaded serving engine for ...
by ZeroTalent on Sunday May 04, 2025 @04:38AM
(#43885409)
Yes, they are doing the Proof of Work. If need be, we will completely emulate human-like mouse movements. These are essentially clients no different from real users.
But the thing is, the more they push for this, the less accessible websites will get, so there has to be another solution. Not everyone uses a mouse.
Source: I work in the industry.
Unfortunately, it seems like browser-use tries to hide that it's controlled by an AI, and uses a typical browser user-agent: https://github.com/browser-use/browser-use/blob/d8c4d03d9ea9...
I'm guessing because of the amount of flags, you could probably come up with a unique fingerprint for browser-use, based on available features, screen/canvas size and so on, that could be reused for blocking everyone using Blast/browser-use.
If calebhwin wanted to make Blast easier to identify, they could set a custom user-agent for browser-use that makes it clear it's Blast doing the browsing for the user.