←back to thread

583 points SweetSoftPillow | 2 comments | | HN request time: 0.57s | source
Show context
vmaurin ◴[] No.45668002[source]
Same goes for age verification.

There was the DNT header, that was a bit to simplistic, but was never implemented https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/...

The thing people need to understand here is that the annoyance is not due to lack of technical solutions, or regulations forcing something. It is explicitly wanted by the industry so they can maximize the consent rate. The browser solution is probably the best technical/user friendly one, but ad tech/data gathering industry won't have any consent. As they control most of the web, they will never do that

replies(4): >>45668031 #>>45668051 #>>45668121 #>>45668873 #
p_l ◴[] No.45668121[source]
Fun fact - if you handle DNT properly, you don't need to show the consent screen... because you're not doing anything requiring said consent.
replies(2): >>45668507 #>>45668948 #
1. voxic11 ◴[] No.45668948[source]
I don't think this is true. DNT being absent or set to consenting is not enough to infer the user has given specific and informed consent under the GDPR.

> Explicit consent: Under the GDPR and similar laws, consent must be specific, informed, and an unambiguous, affirmative action from the user. Consent cannot be assumed by a user's continued browsing or inaction, which is what DNT would require.

replies(1): >>45671129 #
2. p_l ◴[] No.45671129[source]
if DNT is absent you could show GDPR-compliant consent screen (ofc, it would still need to be actually compliant, i.e. with "reject all" button front and center)