I have no relevant insider knowledge and my observation is based purely on the public GitHub thread.Īs I said in a task I opened, we surely don't, but a) we load per-wiki js which might be changed and b) we also serve a lot of third-party software (think of gerrit or jenkins) so I would consider it a "better safe than sorry" measure. Now privacy champion DuckDuckGo has announced that it has released an update to their browser plugin which would block FLoC If you’re a Google Chrome user, you might be surprised to learn that you could have been entered automatically into Google’s new tracking method called Federated Learning of Cohorts (FLoC).
Since the WMF doesn't serve ads (I don't think the fundraising banners count), I don't think WMF sites would be included, so the header would be just cruft (and extra bytes down the wire).ĭisclosure: I work for Google, but I'm making this (and all other) comments in a personal capacity. Our thinking here is that pages detected as including ads-related resources probably fetched something with an ads-related 3p cookie attached, which means it's reasonable to guess that the page visit contributes to some ads profile today.
During the Origin Trial, the default for whether a page will be used for FLoC computation will be based on Chrome's existing infrastructure which detects pages that load ads-related resources.
0 kommentar(er)
