4 ms·
> The most frustrating part of this entire thing is that the intent of the law is pretty clear and yet they are trying stuff like this. GDPR question box imple
by lloeki 3y ago
> The most frustrating part of this entire thing is that the intent of the law is pretty clear and yet they are trying stuff like this.
GDPR question box implementations reveal the true values of implementors. Here are simple heuristics:
1.a is there "accept all" but no "reject all" on the same block, equally weighted and styled identically?
1.b
2. does the question keep coming up regularly when one answers "reject all" but never again as soon as one answers "accept all"?
3.a is the question box modal i.e blocks access or interaction with content?
3.b is the question box non-modal but obscures most of the content?
3.c is the question box non-dismissible or very hard to dismiss?
4. is the question box starting with "We value your privacy"?
re 1. Often there's only a "manage choices" button next to "accept all", and "reject all" is either way down the scaling area of a small modal or entirely absent.
re 2. This is most infuriating, e.g "reject all" cookies having an expiration of 24h and "accept all" cookies having an expiration of 10 years, enticing people to click "accept all" out of pure STOP-PESTERING-ME rage.
re 3. This is equivalent to not answering, and not answering must be treated as if "reject all" was picked, except the choice may not be stored since no explicit choice has been given. Transparent background + 2% opacity light grey crosses outside the question box (either near top right or outright stuffed on top right of the whole browser viewport) overlaid on main content's white background come to mind; that is if they are at all present. Clicking anywhere outside the box should simply dismiss the box and be treated as "I do not answer".
re 4. If you feel like you have to ask me the question and present me with the above, clearly you do not value my privacy, partly because I have DNT set; I know DNT is a "failure" because it was set as default by Edge or something, but then again, I am fairly convinced that given a properly implemented 1. most people would click "reject all" prolly all the time, otherwise the implementors would simply not go to such lengths to have us click "accept all".