News for hackers. Stuff that matters.

A comment on It is not possible to detect and block Chrome headless. Parent comment

Re:It is not possible to detect and block Chrome headless by roywiggins on Thursday January 18, 2018 @02:20PM (#16180390)
Rate-limiting followed by CAPTCHAs seems to be the usual strategy.

I think Google claims to try to detect humans by parsing out their mouse movements and scroll events.

[ Parent | on HN ]
Re:It is not possible to detect and block Chrome headless by nicklaf on Thursday January 18, 2018 @02:51PM (#16180689)
And I can attest that they often presume that I'm a robot.

At this point it would be easier for me to write an alternative frontend to Google search (or just use duckduckgo), but it was be amusing to think that I might evade this by writing a script to simulate mouse movements to appear less robotic.

[ Parent | on HN ]
Re:It is not possible to detect and block Chrome headless by mehrdadn on Thursday January 18, 2018 @04:00PM (#16181395)
> And I can attest that they often presume that I'm a robot.

In my experience this occurs when you are either doing this too much, or you are not accepting their cookies when logged in. (I don't recall the behavior when logged out.)

[ Parent | on HN ]
Re:It is not possible to detect and block Chrome headless by nicklaf on Friday January 19, 2018 @12:09AM (#16184264)
For the record: I was logged out / incognito.

Actually, for whatever reason, this also often seems to cause reCapcha to essentially hellban me and just keep asking for me to solve an endless series of capchas. :/

[ Parent | on HN ]