HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mikewest
privacy-budget
Security & Privacy2019–2025
mikewest / privacy-budget · Archived

privacy-budget

Discover this repository through its Hacker News conversations.

9Distinct people
14Mentions
0Explicit recommenders
208GitHub 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

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, 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 year14 dated mentions

Observed mentions: 2019-08-22 16:54:04 UTC to 2025-11-23 10:07:08 UTC.

012342019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 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
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC303
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
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

3 sources
The initial statement was low on details because it was just an statement of intention. Specific steps they're taking to combat fingerprinting are visible in their public bug tracker[1]. Also, let's not forget the privacy budget[2] system they just announced in the OP. That seems rather promising. [1]: https://bugs.chromium.org/p/chromium/issues/list?q=component... [2]: https://github.com/bslassey/privacy-budget
In Privacy Sandbox – Open standards to enhance privacy on the web
True, it does hand control to browser vendors. But I think I'd rather my browser have control over the information used to personalize ads served to me rather than that information being available to advertisers directly. Google is taking steps to stop excessive fingerprinting[1][2], so it's not like they're just adding new systems for ad personalization without closing off the existing, more intrusive ones. [1]: https://blog.chromium.org/2019/05/improving-privacy-and-secu... [2]: https://github.com/bslassey/privacy-budget
In Privacy Sandbox – Open standards to enhance privacy on the web
Here are the initial proposals from Chrome engineering: > https://github.com/jkarlin/floc > Browsers would need a way to form clusters that are both useful and private: Useful by collecting people with similar enough interests and producing labels suitable for machine learning... This still doesn't address spreading mass propaganda (show feed of immigrant crimes to floc 43A8C before the elections, because well, they happen to be Xenophobic) and user control. They propose browsers send random flocs to avoid clustering flocks of sensitive categories, but pretty sure the default isn't going to be random. -- > https://github.com/bslassey/privacy-budget > Fundamentally, we want to limit how much information about individual users is exposed to sites so that in total it is insufficient to identify and track users across the web, except for poss
Read the rest
ibly as part of large, heterogeneous groups. So, this is a glorified version of Do Not Track but with budgets and involves more telemetry to be shared with browser vendors and/or websites? How is this even in the conversation? How about browsers simply block attempts to fingerprint a user or allow extensions that do? Penalise websites known to fingerprint from search results? Display a big red banner before the user navigates to that website? Proxy such websites, if the user so agrees and send only content that's relevant (like some kind of an advanced read-mode)? -- > https://github.com/dvorak42/trust-token-api#motivation > Preventing fraud is a legitimate use case that the web should support, but it shouldn’t require an API as powerful as a stable, global, per-user identifier. In third party contexts, merely segmenting users into trusted and untrusted sets seems like a useful primitive that also preserves privacy. This kind of fraud protection is important both for CDNs, as well as for the ad industry which receives a large amount of invalid, fraudulent traffic. I like the concept of issuing tokens and then redeeming them later... but it seems like a lot of elaborate crypto to only really prevent ad-fraud (the advanced fingerprinting techniques they talk about elsewhere cannot prevent it?). It opens up another attack surface, whilst also not being truly anonymous to the first-party that issues the tokens. -- > https://github.com/csharrison/conversion-measurement-api > Since the ads industry today uses common identifiers across advertiser and publisher sites to track conversions, these common identifiers can be used to enable other forms of cross-site tracking. > This doesn’t have to be the case, though, especially in cases where identifiers like third party cookies are either unavailable or undesirable. A new API surface can be added to the web platform to satisfy this use-case without them, in a way that provides better privacy to users. This is all out battle against content-blockers. Block third-party cookies, and still you're in their cross-hairs... but wait... this is more privacy-friendly, so will you, the end-user, please suck it up. -- I hope Raymond Hill is reading and already thinking of ways to mitigate this. I see this as push by Chrome in response to the ecosystem Brave is building and the direction Apple is going, and simply taking control of the privacy conversation by doing what's best for them, all around, without holding back any punches. That's not to say, Apple isn't doing the exact same thing! BigTech can't be trusted with privacy, and this post kind of proves it? "It is difficult to get a man to understand something, when his salary depends on his not understanding it." Indeed.
In Privacy Sandbox – Open standards to enhance privacy on the web

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.