Opting Your Website Out of Google's FLoC Network

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

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.
www.influxdata.com
featured
WorkOS - The modern identity platform for B2B SaaS
The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
workos.com
featured

  • chromium-ads-detection

    • If your site does not call document.interestCohort() or include ads, Chrome will already not consider your site in computing FLoC:

    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 load ads or ads-related resources. -- https://web.dev/floc/

    Detecting "ads or ads-related resources" uses a filter derived from EasyList: https://github.com/chromium/chromium-ads-detection/blob/mast...

    (Disclosure: I work for Google, speaking only for myself)

  • floc

    Discontinued This proposal has been replaced by the Topics API.

    • Draft Community Group Report, 13 April 2021, Paragraph 7.1.1:

    "The interest cohort API lives under the Document interface since the access permission is tied to the document scope, and the API is only available if the document is in secure context."

    and

    "The page can opt itself out of the interest cohort computation through the "interest-cohort" policy-controlled feature. [PERMISSIONS-POLICY]" [1]

    [1] https://wicg.github.io/floc/

  • 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.

    InfluxDB logo

  • chromium

    The official GitHub mirror of the Chromium source

    • https://chromium.googlesource.com/chromium/src/+/master/docs...

    > Ad Tagging works by matching resource requests against a filter list (...) to determine if they’re ad requests. Any requests matching the filter are tagged as ads. Further, requests (and some DOM elements such as iframes) made on behalf of previously tagged scripts are also tagged as ads by the AdTracker. An iframe will be marked as an ad iframe if its url matches the filter list, if tagged script is involved in the creation of the iframe, or if its parent frame is an ad iframe. The main frame of a page will never be tagged as an ad. Any request made within an ad iframe is considered an ad resource request.

    I can't find what is included in this filter list, I'm not sure it's open source.

    (mandatory disclaimer: I work at Google, not on Chrome nor ads)

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project