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, 3:59:04 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

14 sources
Chrome does a lot of tracking. This seems obvious enough that I would reply by asking: do you have a source demonstrating that it does not track? However there are many many many sources out there documenting Chrome's comprehensive tracking: - Google's own ToS is probably too long to read, but it lists ways in which you consent to be tracked by the browser - Google's proposals to the W3C for adding new ad-tracking tech to web standards go into detail on Chrome's own mechanisms for doing this tracking as a PoC example [0] - Chrome isn't technically available on iOS; they are forced to use Safari's engine under the hood of iOS Chrome, which restricts in some ways the amount of tracking the browser can do. Despite this, the list of data tracked by iOS Chrome is listed on the AppStore download page and IT IS LONG. Finally, you mention packet
Read the rest
sniffing. In actual fact, direct packet sniffing has been made non-trivial by cert-pinning. This doesn't however prevent checking the frequency and destination of app phone-home requests, and yes, Chrome does it a lot. You can see this yourself if you use common user firewall tools such as LittleSnitch/LuLu/OpenSnitch/etc. [0] https://github.com/WICG/floc#qualifying-users-for-whom-a-coh...
In Firefox 87 trims HTTP Referrers by default to protect user privacy
Yes: https://github.com/WICG/floc > "Whether the browser sends a real FLoC or a random one is user controllable." FLoC stuff is client side. You can send nil FLoC IDs. You can randomize them on every request. You can swap them with your friends. Whatever. Vanilla Chrome might not let you (my money would be on an off-switch but not anything fun) but that's hardly going to be a blocker. (googler but works on something completely unrelated)
In Google’s FLoC Is a Terrible Idea
> it clearly wouldn't be permitted in chrome store (as per well known ad-blockers) Why wouldn't it be permitted? Many ad blockers [1][2][3] are in the Chrome store. Disabling a browser feature is a very standard usage of extensions. > Why wouldn't it be a setting in the browser? It might be! I don't know what Chrome (or other browsers that choose to implement the API) will decide. The proposal is not that far along yet. You could consider filing an issue at https://github.com/WICG/floc/issues > You suggest that the code is in the browser (which i doubt - its certainly not at the moment!) https://github.com/chromium/chromium/tree/master/chrome/brow... [1] https://chrome.google.com/webstore/detail/ublock-origin/cjpa... [2] https://chrome.google.com/webstore/detail/adblock-plus-free-... [3] https://chrome.google.com/webstore/detail/ghoster
Read the rest
In Google to stop selling ads based on your specific web browsing
See https://github.com/WICG/floc > Is it be possible to disable? "A site should be able to declare that it does not want to be included in the user's list of sites for cohort calculation. This can be accomplished via a new interest-cohort permissions policy." For a per-user opt out, a browser extension could easily block it. > Will they be releasing the datasets for how these ML models are constructed? "The browser uses machine learning algorithms to develop a cohort based on the sites that an individual visits. The algorithms might be based on the URLs of the visited sites, on the content of those pages, or other factors. The central idea is that these input features to the algorithm, including the web history, are kept local on the browser and are not uploaded elsewhere — the browser only exposes the generated cohort." This code will b
Read the rest
e in the browser, which is open source. > Do sites in "incogito mode" contribute to analysis? "All sites with publicly routable IP addresses that the user visits when not in incognito mode will be included in the POC cohort calculation." (Disclosure: I work on ads at Google, speaking only for myself)
In Google to stop selling ads based on your specific web browsing
I think the expectation is other browsers will implement by default - the intention incidentally is that FLoC isn’t a google specific tech, it enables private targeting by any ad vendor. The proposal seems to mostly to be by googlers but the association is with WICG which seems to have people from all over. As I noted in my original message - yes, its client side, you can do whatever. (‘Whether the browser sends a real FLoC or a random one is user controllable’ https://github.com/WICG/floc)
In Google to stop selling ads based on your specific web browsing
> if I look up the specs on a pair of Bose QC-35's, I won't get internet-stalked with ads for that specific pair of headphones for the next 3 weeks whenever I pull up a weather report The WSJ seems to be describing https://github.com/WICG/floc, but the kind of remarketing you're describing is what https://github.com/WICG/turtledove is intended to support. Advertisers would still be able to run that kind of personalized ad, but the browser API would not allow them to learn your browsing history in the process. (Disclosure: I work on ads and Google, speaking only for myself)
In Google to stop selling ads based on your specific web browsing

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.