Why a Classic Cdp Bot Detection Signal Suddenly Stopped Working

Posted4 months agoActive4 months ago

avastel

3 points

2 comments

blog.castle.ioTech Discussionstory

informativeneutral

Debate

20/100

Bot DetectionCdpCybersecurity

Key topics

Bot Detection

Cdp

Cybersecurity

Discussion Activity

Light discussion

First comment

47m

Peak period

0-1h

Avg / period

Key moments

01Story posted
Aug 28, 2025 at 9:07 AM EDT
4 months ago
Step 01
02First comment
Aug 28, 2025 at 9:54 AM EDT
47m after posting
Step 02
03Peak activity
2 comments in 0-1h
Hottest window of the conversation
Step 03
04Latest activity
Aug 28, 2025 at 10:03 AM EDT
4 months ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (2 comments)

Showing 2 comments

bediger4000

4 months ago

1 reply

Google does everything it can to prevent adblocking. Then it also does everything it can to make bots undetectable, as this article outlines. Google should watch out, lest people get the impression they're anti-consumer.

avastelAuthor

4 months ago

(Author here) TBH I don't think the main goal of Google was to make bots undetectable. It was more a side effect of preventing side effects while reviewing errors in the devtools: https://source.chromium.org/chromium/_/chromium/v8/v8/+/e08e...

It was the same when Google released the new headless Chrome a few years ago: https://antoinevastel.com/bot%20detection/2023/02/19/new-hea... It made vanilla/naive bots more realistic/detectable by default.

View full discussion on Hacker News

ID: 45051700Type: storyLast synced: 11/18/2025, 12:12:16 AM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

Open link View on HN