The obvious problem we all know, is that a browser cannot distinguish between a functional and an advertisement cookie. And honestly, cookies are a method. There are tracking methods where the user agent has no chance and is not involved.
Also GDPR is addressing much more than tracking consent.
> The obvious problem we all know, is that a browser cannot distinguish between a functional and an advertisement cookie.
Sure it can. Functional cookies come from the domain the user actually visited, advertising cookies come from other domains. That's not always true, but it's true often enough that those should be the defaults.
Firefox even does one better. It has a feature you can enable called "first party isolation" that allows third party cookies, but keeps a different set of them for each domain the user actually visits, so if the user visits a different site none of the third party cookies from the first site are there and they can't be used for tracking between sites.
> Also GDPR is addressing much more than tracking consent.
Next week we'll probably discuss some different part of it that would have been more effective if done some other way.
Also GDPR is addressing much more than tracking consent.