Skip to content

Comment on Proposal: Cookie Consent Should Be Browser-Native, Not Website-Native

Comments

One thing I’d love to hear from the HN crowd:

Are there real technical blockers to browser-native consent management?

* HTTP already has Set-Cookie, so tagging with a Category param seems straightforward.

* Browsers already manage permissions like location, camera, and notifications.

* GDPR/CCPA compliance should be stronger if browsers enforced consent upstream.

Is the real obstacle purely political (ad-tech resistance), or is there something deeper I'm missing on the protocol or standards side?

Also curious: if browsers did offer this, would major sites still try to layer their own consent dialogs on top (to push opt-ins harder)? How would we stop that?

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.