HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
WICG
floc
Makefile2019–2021
WICG / floc · Archived

floc

This proposal has been replaced by the Topics API.

44Distinct people
70Mentions
0Explicit recommenders
926GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This proposal has been replaced by the Topics API.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month70 dated mentions

Observed mentions: 2019-08-22 16:54:04 UTC to 2021-08-17 17:05:28 UTC.

01020302019-08-01 00:00:00 UTC to 2019-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 20192019-09-01 00:00:00 UTC to 2019-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-10-01 00:00:00 UTC to 2019-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-11-01 00:00:00 UTC to 2019-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2020-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-01 00:00:00 UTC to 2020-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-03-01 00:00:00 UTC to 2020-04-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2020-04-01 00:00:00 UTC to 2020-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-01 00:00:00 UTC to 2020-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-01 00:00:00 UTC to 2020-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-07-01 00:00:00 UTC to 2020-08-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2020-08-01 00:00:00 UTC to 2020-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 20202020-09-01 00:00:00 UTC to 2020-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-10-01 00:00:00 UTC to 2020-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-11-01 00:00:00 UTC to 2020-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-12-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2021-02-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2021-02-01 00:00:00 UTC to 2021-03-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2021-03-01 00:00:00 UTC to 2021-04-01 00:00:00 UTC (exclusive): 14 mentions; 1 submissions, 13 comments2021-04-01 00:00:00 UTC to 2021-05-01 00:00:00 UTC (exclusive): 30 mentions; 1 submissions, 29 comments2021-05-01 00:00:00 UTC to 2021-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-06-01 00:00:00 UTC to 2021-07-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2021-07-01 00:00:00 UTC to 2021-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-08-01 00:00:00 UTC to 2021-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 20192019-08-01 00:00:00 UTC2019-09-01 00:00:00 UTC101
Sep 20192019-09-01 00:00:00 UTC2019-10-01 00:00:00 UTC000
Oct 20192019-10-01 00:00:00 UTC2019-11-01 00:00:00 UTC000
Nov 20192019-11-01 00:00:00 UTC2019-12-01 00:00:00 UTC000
Dec 20192019-12-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
Jan 20202020-01-01 00:00:00 UTC2020-02-01 00:00:00 UTC000
Feb 20202020-02-01 00:00:00 UTC2020-03-01 00:00:00 UTC101
Mar 20202020-03-01 00:00:00 UTC2020-04-01 00:00:00 UTC303
Apr 20202020-04-01 00:00:00 UTC2020-05-01 00:00:00 UTC000
May 20202020-05-01 00:00:00 UTC2020-06-01 00:00:00 UTC000
Jun 20202020-06-01 00:00:00 UTC2020-07-01 00:00:00 UTC101
Jul 20202020-07-01 00:00:00 UTC2020-08-01 00:00:00 UTC312
Aug 20202020-08-01 00:00:00 UTC2020-09-01 00:00:00 UTC000
Sep 20202020-09-01 00:00:00 UTC2020-10-01 00:00:00 UTC000
Oct 20202020-10-01 00:00:00 UTC2020-11-01 00:00:00 UTC000
Nov 20202020-11-01 00:00:00 UTC2020-12-01 00:00:00 UTC000
Dec 20202020-12-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
Jan 20212021-01-01 00:00:00 UTC2021-02-01 00:00:00 UTC606
Feb 20212021-02-01 00:00:00 UTC2021-03-01 00:00:00 UTC404
Mar 20212021-03-01 00:00:00 UTC2021-04-01 00:00:00 UTC14113
Apr 20212021-04-01 00:00:00 UTC2021-05-01 00:00:00 UTC30129
May 20212021-05-01 00:00:00 UTC2021-06-01 00:00:00 UTC101
Jun 20212021-06-01 00:00:00 UTC2021-07-01 00:00:00 UTC404
Jul 20212021-07-01 00:00:00 UTC2021-08-01 00:00:00 UTC000
Aug 20212021-08-01 00:00:00 UTC2021-09-01 00:00:00 UTC101

What Hacker News says

30 sources
FLoC is Google's loophole after disabling third-party cookies in Chrome and promising they "will not build alternate identifiers to track individuals as they browse across the web"[0]. FLoC is a new tracker to replace third-party cookies, but it works by putting users in groups and tracking those groups, so they technically aren't tracking "individuals" this time. Except you can use FLoC to track individuals by identifying them as a unique intersection of many disparate groups[1]. [0] https://www.theverge.com/2021/3/3/22310332/google-privacy-re... [1] https://github.com/WICG/floc/issues/100
In GitHub blocks FLoC across all of GitHub Pages
Cloudflare, Akamai, Fastly and other CDNs should disable FLoC by default for all customers, and provide a toggle to those customers who explicitly wish to enable it. But until they do[1]: Apache: Header always set Permissions-Policy: interest-cohort=() Caddy: header Permissions-Policy "interest-cohort=()" Cloudflare Workers (not free as there are limits): addEventListener('fetch', event=> { event.respondWith(handleRequest(event.request)) }) async function handleRequest(request) { let response=await fetch(request) let newHeaders=new Headers(response.headers) newHeaders.set("Permissions-Policy","interest-cohort=()") return new Response(response.body, { status: response.status, statusText: response.statusText, headers: newHeaders })
Read the rest
} Lighttpd: server.modules +=("mod_setenv") setenv.add-response-header=("Permissions-Policy"=>"interest-cohort=()") Netlify: [[headers]] for="/*" [headers.values] Permissions-Policy="interest-cohort=()" Nginx: add_header Permissions-Policy interest-cohort=(); [1] https://github.com/WICG/floc#opting-out-of-computation
In GitHub blocks FLoC across all of GitHub Pages
It's sort of opt-in. For websites, FLoC cohort computation only triggers if you call the document.interestCohort API or load ads - these actions are considered an opt-in. (https://github.com/WICG/floc/issues/103) For users, it's sort of opt-in, too: You must be logged into a Google account, must have enabled Chrome history data sync, must not block third-party cookies, must have enabled Google web activity tracking and must have enabled ad personalization. (https://github.com/WICG/floc#qualifying-users-for-whom-a-coh...) Also, you can disable FLoC via chrome://settings/privacy or chrome://flags. (https://github.com/WICG/floc/issues/103#issuecomment-8218146...) It's not a perfect opt-in, but it's also not malware.
In Proposal: Treat FLoC as a security concern
I've not been following this proposal closely I did find https://github.com/WICG/floc >Tracking people via their cohort >A cohort could be used as a user identifier. It may not have enough bits of information to individually identify someone, but in combination with other information (such as an IP address), it might. Whose purpose is: >A FLoC cohort is a short name that is shared by a large number (thousands) of people, derived by the browser from its user’s browsing history. I wonder if it's possible to define a large enough number X that people are OK with the idea. (Cookies are effectively "1" and nothing is "3,010,000,000" ie on the internet) Could the cohort minimum size be configurable? Given the IP address can be known today: what's the existing accidental "FLoC proxy" or "How unique are you online?" Or "online finger print" (some
Read the rest
thing I'd not thought of before: my timezone can significantly narrow down who I am) You can try using yourself on: https://amiunique.org/fp
In Proposal: Treat FLoC as a security concern
> What adding this header does is exclude your website from being used when calcualting a user’s cohort. Cohorts are calculated locally from browsing history; sites that send this header will be excluded from this calculation. That's exactly the point, so where's the misinformation? Edit: The information from Google seems to be contradictory. From https://web.dev/floc/ > 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. This seems to imply that not calling document.interestCohort() (or not having ads on the page during the trial) is the same as opting out. But then on https://github.com/WICG/floc#opting-out-of-computation > A site should be able to declare that it does not want to be included in the user's list of sites for cohort calcula
Read the rest
tion. This can be accomplished via a new interest-cohort permissions policy. This policy will be default allow. This makes a lot more sense. Why would Google want to exclude sites from calculations just because they don't make use of the FLoc cohort themselves?
In Misinformation about Permissions Policy and FLoC
Apple uses segments for itself, FLoC is a web standard, so third-parties can de-anonymize as a side-effect: https://github.com/WICG/floc/issues/100 Frankly the same problem exists in PCM’s, Apple’s proposed solution to allow private tracking from ad clicks: https://github.com/privacycg/private-click-measurement/issue... However, both of these are solutions to help web developers of third-party sites and ad networks track end users anonymously. All would argue that they’re better than third-party cookies, though in reality, users might want to turn off or opt out of both of these anonymize tracking devices. Another way of putting it: I don’t mind sharing my data with Apple when Apple says to trust them. I also don’t mind sharing data with Google when Google says to trust them. I do both on a regular basis with iCloud and Google Drive for e
Read the rest
xample. What I have a problem with is when people try to “solve” third-party cookies in a way that doesn’t increase privacy but simply pretends to. I’m not against first party telemetry data, I love it as an engineer and I know that bugs found and reported with it can be fixed, thus improving my experience with products. What I dislike is when advertising companies can sign deals with Google or Facebook and gain access to lots of info about how well their campaigns are working, or when I don’t know when my data is being used, or when companies start messing with DNS so third-parties look like first-party just to increase revenue. To me it says it all that Google apparently turns off FLoC when inside GDPR zones. Only stronger laws will actually prevent bad behaviour on legitimate rule-abiding services. Only providing less and less means of tracking can we truly start to prevent it technically. Looking for replacements to tracking to support existing business models is doomed to failure as long as people can keep voting, literally and figuratively, for privacy-preserving alternatives and policies.
In FLoC Away from Chrome

Showing the 15 most recent of 30 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.