HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
patcg-individual-drafts
topics
Bikeshed2022–2024
patcg-individual-drafts / topics · Archived

topics

The Topics API

19Distinct people
24Mentions
0Explicit recommenders
874GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 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 year24 dated mentions

Observed mentions: 2022-01-25 13:30:23 UTC to 2024-09-15 22:14:57 UTC.

0510152022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 3 submissions, 7 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

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
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC1037
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC13013
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

10 sources
> I don't have hundreds of cookies set by any website Are you sure? These are third-party cookies, and it's not easy to get a full list. One way to do it is to go to a major publisher (NYT, CNN, etc) with devtools open and networking enabled. Filter to third party requests and look for ones sending cookies. Trying this on the NYT front page I saw 3p requests with cookies to amazon-adsystem.com, doubleclick.net, prebid.media.net, rubiconproject.com, adnxs.com, 3lift.com, openx.net, google.com, scorecardresearch.com, casalemedia.com, pubmatic.com, bluekai.com, adsrvr.org, bing.com, twitter.com, everesttech.net, criteo.com, dotomi.com, bidswitch.net, mfadsrvr.com, agkn.com, pswec.com, adtdp.com, demdex.net, bidr.io, adition.com, brand-display.com, intentiq.com, w55c.net, pippio.com, rlcdn.com, and adsymptotic.com before I got bored and s
Read the rest
topped counting. Some of these might not be for personalized advertising, but most of them look like it. > browsers would be incentivized to implement with good intentions. Browsers compete on privacy, and what they do is open source. So while their incentives aren't perfect, external groups (and competing browsers!) can help keep them honest by paying attention and calling attention to bad decisions. A great example of this was Mozilla's thorough and careful privacy analysis of FLoC (https://blog.mozilla.org/en/privacy-security/privacy-analysi...), and looking at Topics (https://github.com/patcg-individual-drafts/topics) Chrome seems to have spent a lot of time addressing that feedback.
In Protecting Against Browser-Language Fingerprinting
FLoC was a proposal for targeted advertising ("how do you figure out who to show your ads to?"), and FLoC 2.0 is the Topics API proposal: https://github.com/jkarlin/topics Mozilla's proposal here is for conversion tracking ("how do you figure out whether your ads are working?"). It is an alternative to proposals by Apple (https://webkit.org/blog/11529/introducing-private-click-meas...) and Google (https://github.com/WICG/conversion-measurement-api) (Disclosure: I work on ads at Google, speaking only for myself)
In Privacy preserving attribution for advertising
Here is one way to disable "FLoC" chrome://settings/privacySandbox Evolution from FLoC FLoC ended its experiment in July of 2021. We've received valuable feedback from the community^1 and integrated it into the Topics API design. A highlight of the changes, and why they were made, are listed below: FLoC didn't actually use Federated learning, so why was it named Federated Learning of Cohorts? This is true. The intent had been to integrate federated learning into FLOC but we found that on-device computation offered enough utility and better privacy. FLoC added too much fingerprinting data to the ecosystem The Topics API significantly reduces the amount of cross-site identifiable information. The coarseness of the topics makes each topic a very weak signal; different sites receiving different topics further dilutes its utility for fingerpri
Read the rest
nting. Stakeholders wanted the API to provide more user transparency The Topics API uses a human-readable taxonomy which allows users to recognize which topics are being sent (e.g., in UX). Stakeholders wanted the API to provide more user controls With a topic taxonomy, browsers can offer a way (though browser UX may vary) for users to control which topics they want to include The Topics API will have a user opt-out mechanism FLoC cohorts might be sensitive FLoC cohorts had unknown meaning. The Topics API, unlike FLoC, exposes a curated list of topics that are chosen to avoid sensitive topics. It may be possible that topics, or groups of topics, are statistically correlatable with sensitive categories. This is not ideal, but it's a statistical inference and considerably less than what can be learned from cookies (e.g., cross-site user identifier and full-context of the visited sites which includes the full url and the contents of the pages). FLoC shouldn't automatically include browsing activity from sites with ads on them (as FLoC did in its initial experiment) To be eligible for generating users' topics, sites wil have to use the API. https://github.com/jkarlin/topics It is remarkable to me that Google can freely experiment on whomever they wish. If the experiments demonstrate negative effects, e.g., generation of execssive amounts of fingerprinting, it's unfortunate for those who were swept up in these "experiments". Why not ask users if they want to volunteer to particpate in a trial/experiment. Imagine if drug companies did not obtain permission to test their compounds on new patients. Instead they just substituted the new drug into what they sold on the market. Same label. Chrome is Chrome, right. Nevermind all the undisclosed variations and experiments. For example, "field trials" identified by only a number. This is hardly informed disclosure and consent. 1. This is amusing. What users were solicited for feedback. Perhaps they are referring to some surveillance they conducted, looking for mentions of FLoC.
In Rebranding FLoC Without Addressing Key Privacy Issues
There’s a couple of important things to note here. First, the new Permissions-Policy: browsing-topics=() (or the old FLoC Permissions-Policy: interest-cohort=()) will ban this functionality, which is nice if you don’t want to leak your user’s data to Google for advertising purposes. I just checked and my site is still sending it so nothing to worry about here. Secondly, the initial list of topics can be found at https://github.com/jkarlin/topics/blob/main/taxonomy_v1.md . “/Finance/Grants, Scholarships & Financial Aid” is interestingly scary as a target group. They’re also weirdly American (“/Finance/Insurance/Health Insurance”, putting reggae under “World Music”, etc.)
In Get to Know the New Topics API for Privacy Sandbox

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.