-
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.
First party sets are a centralized list of sites that act as one logical site. The list is gated by the browser vendor. Details here (https://github.com/GoogleChrome/first-party-sets/blob/main/F...).
This is intended to deal with the technical challenge that when company A buys company B, the process of fusing the auth rules so that being logged into A implies a login to B is a colossal nightmare project under first-party-only rules. So, for example, this lets Facebook declare that fbcdn.net is in the same FPS as facebook.com to simplify resource serving. What it should not allow is for joe-random-domain.com to declare that the DoubleClick ad endpoints are first-party to them.
https://github.com/WICG/first-party-sets#non-goals has:
Non-goals: ... Information exchange between unrelated sites for ad targeting or conversion measurement.
To get something onto the list (https://github.com/GoogleChrome/first-party-sets/blob/main/f..., currently empty) you need to make a public PR with rationale (https://github.com/GoogleChrome/first-party-sets/blob/main/F...). It doesn't look to me like DoubleClick would qualify?
Why would they need to? DoubleClick literally has a built in backdoor with the undisclosed and impossible to disable "X-Client-Data" telemetry header.
DoubleClick is hard coded into every Chrome browser :) [1]
[1] https://chromium.googlesource.com/chromium/src/+/e51dcb0c148...