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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM 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

70 sources
With cross-site cookies, adnetwork.com has full information about what sites you've visited (among sites that incorporate their cookies). This isn't good either! But generally speaking, an individual site using adnetwork.com for advertising won't have or want access to that vector of your interests; many site operators don't even have visibility into what ads win real-time bidding, just that they're receiving money for providing their inventory. Certainly there are players that can provide demographic targeting metadata to site operators, but to my knowledge they are less widely known and certainly not cheap, and I imagine (or hope) any players with wide enough cookie reach would be discouraged from maintaining a database that could associate metadata with PII. With FLoC, though, the idea was that the browser would provide document.intere
Read the rest
stCohort() and the individual site's JS could react accordingly: https://github.com/WICG/floc . This means that any site, regardless of its contracts with ad networks, could immediately identify your cohort and associate it with your activity. Web developers working in good faith would be encouraged to have user.cohort or user.topic fields from day one "just so you have it" - imagine all the ways someone could use this in bad faith. Inevitably this data would leak (or be intentionally leaked) and could trivially become a target list for doxxing closeted people. It's a dangerous, dangerous proposal.
In Google considers switching FLoC to a topic-based approach
It's pretty complicated and my understanding could be wrong and definitely not an expert. All the stupid CIA-style names that keep changing don't help. Turtledove, fledge, sparrow lol. But from what I think I know that's kind of right technically, but kind of not in terms of actual real privacy. Yes, the actual browsing data, e.g. for the basic floc cohorts only what amazon product page you visited, is no longer 'sent' to ad networks (that's a pretty big oversimplification of how ad networks track you but for brevity). That data is parsed in your browser to generate a cohort ID for you. But this cohort ID is exposed to the world document.interestCohort() and is what's used for targeting and tracking. To me it seems that the cohorts are so small "thousands of people" + IP or UA it's basically the same as a semi-long lasting uuid. And if yo
Read the rest
u have like even 10 different cohort IDs, even if some of them are 'fake'/'noise' that's probably enough to ID you alone Here's an image from google's site. https://web-dev.imgix.net/image/80mq7dk16vVEg8BBhsVe42n6zn82... It also seems like Chrome/google might be still defaulting browser settings to give themselves even more data just like they currently do? https://github.com/WICG/floc#qualifying-users-for-whom-a-coh... BUT when you layer on the other proposals (Fledge/Turtledove/Dovekey or whatever) - which I don't understand that much maybe someone else can explain - it seems like it basically collect this page/product level data and makes it available to DSP etc for tracking/ad serving (again if not technically 1:1 basically in consequence given the sizes of these groups). Like one of the proposals talks about a 'trusted' key/value server which doesn't seem that different from what already happens? The original proposal wanted to move the entire ad bid/target/serve process into the browser.
In Amazon is blocking Google’s FLoC
> Google must not, and cannot implement FLOC without it being a cross-browser standard; that is to say if anyone of Microsoft, Apple or Mozilla veto FLOC, it's dead. This is how standards are supposed to work. This isn't how internet standards work, or the how they have ever worked. Take the development of HTTP/2: [2009] Google researches how HTTP could be improved and develops SPDY: https://blog.chromium.org/2009/11/2x-faster-web.html https://dev.chromium.org/spdy/spdy-whitepaper [2010] Chrome implements SPDY, and they start gathering real world performance data. [2011] Several rounds of iteration to make it faster, more reliable, and fix bugs. [2012] Major websites built out support, Firefox adds support, the process of standardizing it with the IETF begins: https://datatracker.ietf.org/doc/html/draft-mbelshe-httpbis-... [2013] More an
Read the rest
d more sites build support, CDNs enable it by default [2014] Safari adds support. [2015] Standardized as HTTP/2: https://datatracker.ietf.org/doc/html/rfc7540 Standardization follows cross browser support, and cross browser support follows single browser support. This is the path FLoC is following: it's currently incubated under the WICG (https://github.com/WICG/floc) and Chrome is developing it. Other browsers are paying attention and evaluating: that's what this Mozilla article is about. If at some point we get to a version that other browsers are happy with and choose to implement, then it could potentially be standardized. (Disclosure: I work on ads at Google, speaking only for myself)
In Privacy Analysis of FLoC
FLoC as a source of fingerprinting bits has been an issue in W3C discussions of the project. https://github.com/WICG/floc/issues/69 As a fingerprinting surface FLoC has similar properties to the Battery Status API -- not stable for the same user over long intervals, but can be used to help match pageviews from different domains that were close in time. https://www.schneier.com/blog/archives/2016/11/firefox_remov...
In Ad tech firms test ways to connect Google’s FLoC to other data
I am really puzzled by the negative sentiment around adtech on Hacker News, especially since I would guess that a lot of people here have a salary that depends directly or indirectly on advertising. "Tracking" gets a lot of bad press, so much so that I sometimes wonder if this is not organized by the tech giants (Apple, Google, Facebook) who have access to their own first party and who thus have much less to lose when cross site tracking disappears. Adtech providers only have access to products you buy/see, for a limited time and without any personal data, meanwhile Google and Facebook know everything about you, your friends, your center of interests the places you go to, along with your name but somehow everyone seems hell-bent on abolishing 3rd-party cookies. Apple's own apps are not subject to this change, and as noted by other comment
Read the rest
ers this will probably shift budgets to subscription of which Apple takes its cut. All this will further the supremacy of walled-gardens and big tech, at the expense of smaller independent players. I'll be honest, there is a creepy feeling when being tracked cross-site, and adtech providers have collectively failed at providing explanations, and a transparent account of how this works and why this is useful. They have also relied on fingerprinting, which has hurt the credibility of the field. The issue is that the replacement that are currently in the works (https://github.com/WICG/floc and https://github.com/WICG/turtledove/blob/main/FLEDGE.md) are extremely complex, will still dramatically impact adtech performance and only improve privacy for a very contrived definition of the concept which incidentally benefits once again big tech vendors... As to the effectiveness of advertising, removing tracking will have a huge impact. And this affects all players in the value chain, not only adtech providers but also publishers and more importantly advertisers which will see their return on ad spent severely impacted. There is a real of loss "social welfare" (I mean in a game-theoretic sense, but also for real if you believe in capitalism) if tracking is disabled. The freakonomics article gets cited a lot but the industry as a whole is moving forward with a greater emphasis on proving incremental sales. Advanced clients (who can spend billions per year) have real statisticians doing permanent randomized control trials proving that every dollar spent is providing incremental sales. I work for an adtech company and we have automatic RCTs for every single client, and guess what, advertising works for most clients. This is on top of fact that we are measuring the effectiveness of dollars spent on us, in addition to the dollars spent on competitors/other channels on which we have no control of course. The fact that Uber could see no impact when going from 150m to 50m is a testament to the incompetency of their CMO, which could not be bothered to actually measure and pilot the campaigns correctly, not the effectiveness of adtech as a whole. Thoughts are my own not my employer's.
In iOS 14 tracking changes sees big ad spending drop, tumbling prices
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

Showing the 15 most recent of 70 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.