Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
proposals
A home for well-formed proposed incubations for the web platform. All proposals welcome. (by WICG)
-
you can target an Economist reader a week later on a different website. If FLoC works, you can still do that.
https://github.com/WICG/floc won't really let advertisers do that, this is what https://github.com/WICG/turtledove is for
(Disclosure: I work on ads at Google, speaking only for myself)
you can target an Economist reader a week later on a different website. If FLoC works, you can still do that.
https://github.com/WICG/floc won't really let advertisers do that, this is what https://github.com/WICG/turtledove is for
(Disclosure: I work on ads at Google, speaking only for myself)
Chrome's FLoC and TURTLEDOVE proposals are nascent web standards under the Web Incubator Community Group (https://wicg.io). My understanding is that Chrome is hoping to come up with something that other browsers also like?
Other browsers are working on this general project ("how do you do ads without cookies") too: Edge has https://github.com/WICG/privacy-preserving-ads/blob/main/Par... and Safari has https://webkit.org/blog/8943/privacy-preserving-ad-click-att...
Yes, the primary tool is CNAME cloacking. On Firefox, uBlock Origin already detects and blocks this. Unfortunately Chrome and Safari don't expose the APIs to allow this there.
https://github.com/uBlockOrigin/uBlock-issues/issues/780