8 ms·

This kind of post that provides no context will lead to cargo-cult, with people blindly copying and pasting these directives, and believing they have increased

This kind of post that provides no context will lead to cargo-cult, with people blindly copying and pasting these directives, and believing they have increased the privacy of their site... If your web site does not include ads, FLoC is already disabled. Here, "ads" mean ads that EasyList can detect. This HTTP header will just make your config more complex and your responses slightly bigger, with no change of behaviour. If you include external ads on your pages, then I doubt disabling FLoC will increase your visitors' privacy, but at least this header will have a real effect.

feross 5y ago
> If your web site does not include ads, FLoC is already disabled Citation? Here's what the FLoC explainer says: > All sites with publicly routable IP addresses that the user visits when not in incognito mode will be included in the POC cohort calculation. https://github.com/WICG/floc#sites-which-interest-cohorts-will-be-calculated-on https://github.com/WICG/floc#sites-which-interest-cohorts-wi... This sounds to me like all sites, whether they contain ads are not, are used to cluster users into cohorts.
- idoubtit 5y ago
  From https://web.dev/floc/ https://web.dev/floc/ in section "Do websites have to participate and share information?" > For pages that haven't been excluded, a page visit will be included in the browser's FLoC calculation if document.interestCohort() is used on the page. > During the current FLoC origin trial, a page will also be included in the calculation if Chrome detects that the page loads ads or ads-related resources.
  - deleted 5y ago
    [deleted]