Hacker News Reader

The listed use-cases are not what I typically see complaints about.

What I do see a lot: * This will be used to detect and block ad blockers. * Open source users can't do attestation and will get locked out of parts of the web.

These are not goals of this proposal from what I can tell. And there are indeed discussions how to avoid those negative externalities.

View on HN

"Users like visiting websites that are expensive to create and maintain, but they often want or need to do it without paying directly. These websites fund themselves with ads, but the advertisers can only afford to pay for humans to see the ads, rather than robots."

That's as clear as day, they won't let you view the page with ad blocking.

That's debatable. I read it like this only affects the charging model. Advertisers only get charged for impressions from humans, not bots. This is enough to prevent fraud.

Once the API is there it can be used for forbidding ad blockers.

Reply on news.ycombinator.com