The actually ridiculous part is not that.
It’s the fact that our browsers don’t solve this issue in a standardized way.
Everyone who serves HTTP in the Eu and includes third party tracking, shows you an idiosyncratic consent banner. Often these things download a large amount of JS as well.
That’s completely and utterly idiotic.
- It’s confusing for users.
- It interrupts the user’s flow everytime they visit a site.
- It’s bad for overall performance.
- It’s bad for people who publish content.
- Developers have to defer to legal experts for trivial stuff out of FUD.
- It doesn’t work correctly on the technical side.
- It doesn’t work from a user’s perspective, because they just get annoyed or uncertain and falsely consent!
Nobody wins.
It should just be a standard, global feature in browsers. A site should only ask you _once_, if at all from a user’s perspective.
The browser should send a “profiling and tracking” whitelist, or simply make it available via a JS API.
Why is this not the case?
It’s the fact that our browsers don’t solve this issue in a standardized way.
Everyone who serves HTTP in the Eu and includes third party tracking, shows you an idiosyncratic consent banner. Often these things download a large amount of JS as well.
That’s completely and utterly idiotic.
- It’s confusing for users.
- It interrupts the user’s flow everytime they visit a site.
- It’s bad for overall performance.
- It’s bad for people who publish content.
- Developers have to defer to legal experts for trivial stuff out of FUD.
- It doesn’t work correctly on the technical side.
- It doesn’t work from a user’s perspective, because they just get annoyed or uncertain and falsely consent!
Nobody wins.
It should just be a standard, global feature in browsers. A site should only ask you _once_, if at all from a user’s perspective.
The browser should send a “profiling and tracking” whitelist, or simply make it available via a JS API.
Why is this not the case?