Comment 3 for bug 1926218

'find "$HOME"/snap/chromium -iname *floc*' gives me nothing either, but I only installed it a couple of weeks ago.

Some things I observe:

1. In my set-up, Floc can _not_ be enabled in <chrome://settings/privacySandbox>.

2. Look into the parts concerning Floc in the source code, one finds several stub functions, e.g. in chrome/browser/privacy_sandbox/privacy_sandbox_service.cc:393

  void PrivacySandboxService::SetFlocPrefEnabled(bool enabled) const {
    // TODO(crbug.com/1299720): Remove this and all the UI code which uses it.
    return;
  }

3. In that page <crbug.com/1299720>,

> FLoC-the-feature has been removed from the codebase, but there are still a few UX surfaces that need to surface FLoC information (basically informing users that it's disabled).
>
> To support this, while also transitioning to Privacy Sandbox Settings 3, many functions have been left with stubs with little or no functionality.
>
> Once Privacy Sandbox Settings 3 has been launched, these surfaces are no longer required, and the remaining functions can be cleaned up.

And then the title of commit https://chromium.googlesource.com/chromium/src/+/3c4b23ea94bf0efbc12d93e832b5888c50412b6b is

> Privacy Sandbox Settings: Move FLoC to Topics API

This suggests Google is moving away from Floc.

4. Indeed, from <https://developer.chrome.com/docs/privacy-sandbox/topics/#how-does-the-topics-api-address-concerns-with-floc>,

> The origin trial of FLoC in 2021 received a wide range of feedback from adtech and web ecosystem contributors. In particular, there were concerns that FLoC cohorts could be used as a fingerprinting surface to identify users, or could reveal a user's association with a sensitive category. There were also calls to make FLoC more transparent and understandable to users.
>
> The Topics API has been designed with this feedback in mind, to explore other ways to support interest-based advertising, with improved transparency, stronger privacy assurances and a different approach for sensitive categories.

All in all, apparently Floc is being phased out we have a moving target. So, if that is a correct assessment, although this bug report will technically solve itself with time (insofar as it is targeted at Floc), we will still keep an eye for future tracking mechanisms inside Chromium, under whatever name they may come to be.