-
The TCF2.0 system is terrible, it is a model of technically correct but bad-in-spirit compliance for GDPR and as an engineer it drives me up the wall. I hate the idea that it is going to swallow up __uspapi in the new GPP proposal the IAB is working on.Permalink On twitter.com
♻️ 5 Retweets
❤️ 8 Favorites
Mood -6 🙁
-
I understand we're now working in it's shadow regardless... but if I was starting from zero on this concept I would not make a single choice the same way.Permalink On twitter.com
Mood 0
-
I like __uspapi. That's basically how GDPR consnet should work. This entirely nonsense idea that anyone would consent to one individual ad tech provider but not another is just ridiculous and the framework that had to be built up to support that is equally ridiculous...Permalink On twitter.com
❤️ 2 Favorites
Mood -2 🙁
-
I can't imagine any non-tech/ad-tech-employed user has ever gone into the Nightmare Panel of the CMP and gone 'yeah, I'm going to consent to have my data used by ad6media but not Threedium'. That has never ever happened & if you say it did I guarantee you are lying or misled.Permalink On twitter.com
♻️ 1 Retweets
❤️ 7 Favorites
Mood +3 🙂
-
TCF is really one of those rare cases where the more I work with it and understand it the less I like it. It's the inverse of growing on me, it's like a memetic cancer.On twitter.com
Mood +4 🙂
-
The fact that GDPR as a regulation allows TCF to exist in its current format is a failure of lawmaking and regulation and embarrassing to the entire EU.Permalink On twitter.com
♻️ 1 Retweets
❤️ 5 Favorites
Mood -4 🙁
-
It's very clear the number of people who care about the issues of the technical mechanisms of this very specific technology and the UIs it enables is like... me and few enough other people that we'd be full on maaaaybe two pizzas... but GAHPermalink On twitter.com
Mood +5 🙂