HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
WICG
first-party-sets
Bikeshed2020–2025
WICG / first-party-sets · Archived

first-party-sets

Discover this repository through its Hacker News conversations.

7Distinct people
8Mentions
0Explicit recommenders
401GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

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, 4:59:52 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 year8 dated mentions

Observed mentions: 2020-09-11 13:34:04 UTC to 2025-05-02 22:33:09 UTC.

012342020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

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
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

4 sources
> if it would hasten the demise of 3rd party cookies Will FLoC speed this up? As far as I know, Firefox, Chrome, and Safari are already largely publicly committed to phasing out 3rd party cookies over the next couple years. I guess FLoC might move that deadline up a bit? But I suspect some critics of FLoC are looking at the proposal as a compromise that we don't need to make. The thinking is, at the point where we have public statements from every single major browser, including Chrome and Edge, that 3rd party cookies are going to get phased out, why do we need to throw the advertising industry a bone? We won this particular fight, 3rd party cookies are going out the door. Now (the thinking is) we just need to make sure that counter-proposals like FLoC and FPS[0] don't reverse the gains we've made. I'm not completely sure how to character
Read the rest
ize Google's recent proposals, but an arguably reasonable take that I've seen online is that Google somehow got peer-pressured into making a very public commitment to remove 3rd-party cookies, that they no longer feel they can back down from that commitment, and that a lot of their recent proposals seem to be attempts to find some way to get out of that deal. First Party Sets in particular are just a very conveniently timed proposal. I suspect this take is at least a little simplistic, but if it is at all accurate then now is a very good time to increase pressure on Google, not decrease it. So I think we might be in a situation where the onus is on people proposing compromise to prove that compromises will make a difference, because I don't take it for granted at this point that FLoC's acceptance or rejection will change anything about how 3rd party cookies are handled in the future. [0]: https://github.com/privacycg/first-party-sets
In Nobody is joining Google's FLoC
How would you propose handling this with DNS? Here are some things it covers: * a.example.com and b.example.com are the same site * a.co.uk and b.co.uk are not the same site * a.cloudfront.net and b.cloudfront.net are not the same site * a.higashikawa.hokkaido.jp and b.higashikawa.hokkaido.jp are not the same site * a.example.higashikawa.hokkaido.jp and b.example.higashikawa.hokkaido.jp are the same site There is a proposal to do something similar using response headers and .well-known urls: https://github.com/privacycg/first-party-sets
In Google Safe Browsing can kill a startup
I didn’t see it mentioned but a common use case for 3rd party cookies is correlating session data across your own multiple domains (if your company owns multiple domains). Publishing companies typically own multiple domains/verticals and can increase ad revenue / seo / traffic quality by linking properties together. It’s important to be niche as a site (verticalization) but also broad as a publishing operation (own many verticals and shift your marketing spend daily). Anyways, google has been writing a spec for “first party sets” to help replace the use of a 3rd party cookie to connect domains you own. https://github.com/privacycg/first-party-sets I believe this will need to be implemented before Chrome moves aggressively against 3rd party cookies.
In Google Chrome browser privacy plan investigated in UK

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.