-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autoconsent standard #39
Comments
To the best of my knowledge there is no such standard yet. IMHO, it would be a good idea to have a standardize way that developers can opt-in; there is a shared incentive to avoid site breakage (both from website or cookie-consent developers and from content blockers). It would reduce complexity from the content blocker side (not having to re-engineer detection rules), and it would give more control to the developers of the website or framework to quickly fix some issues without having to wait until a fix lands. Though I'm in favor, I fear our abilities to push for a standard that will get adoption is limited. Maybe a practical approach would be to start defining such a element in the page and then the auto-consent rules could migrate to that (for the individual site or the consent framework). If more websites or framework would adopt it, it would make sense to implement a detecting in the auto-consent library to automatically detect it (without manually creating a rule). Would be worth discussing with member of the DuckDuckGo team. They are driving the development of the library and maintaining the rules (https://github.com/duckduckgo/autoconsent/). cc @sammacbeth |
Thanks for your quick response @philipp-classen, really appreciate it! |
Not as much an issue, more a request.
I would like to suggest an autoconsent-standard that can be used by website-developers / cookie-consent developers.
Assume a website has the following code for the cookie-consent's "OK" button:
<a data-autoconsent="true">OK</a>
Then this could work as follows:
data-autoconsent
attribute;Perhaps a standard already exists, if so please let me know. I'm looking forward to your opinion :)
The text was updated successfully, but these errors were encountered: