-
ffs the IABTechLab multi-state privacy specification was so rushed out the door they have apparently forgot to include a non-applicable signalPermalink On twitter.com
-. github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/tree/main/Sections/US-States
♻️ 2 Retweets
❤️ 9 Favorites
Mood -1 🙁
-
Every signal needs to note if the user is verified as not having the law apply to them at each state level. In CA this is represented byPermalink On twitter.com
1---. This *needs* to be here and is different from0in the spec. This is needed for any opt-out system.
❤️ 5 Favorites
Mood 0
-
The IAB has given us *14 days* to respond to both this complex spec AND the complex legal binding that intends to support it. This is because they are rushing this solution and the end result is clearly mistakes. This is a *problem*.On twitter.com
❤️ 4 Favorites
Mood +1 🙂
-
The IAB should withdraw the Multistate Spec, tell people to use USPAPI until further notice, and spend the time to do a multistate approach *right*.Permalink On twitter.com
Mood 0
-
Better to not release at all then to do a half-ass job of compliance with the law.Permalink On twitter.com
Mood +2 🙂