HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
michaelkleber
privacy-model
Web Development2019–2022
michaelkleber / privacy-model · Archived

privacy-model

A Potential Privacy Model for the Web: Sharding Web Identity

6Distinct people
7Mentions
0Explicit recommenders
205GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A Potential Privacy Model for the Web: Sharding Web Identity

GitHub

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 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 year7 dated mentions

Observed mentions: 2019-08-22 17:47:33 UTC to 2022-07-28 00:31:35 UTC.

01232019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022

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 UTC312
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC211
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202

What Hacker News says

7 sources
> There are a handful of companies that can track you across multiple websites, so any real solution has to start by enumerating and addressing those companies. I think it's more like hundreds than handfuls. But they're all connecting your behavior across sites using the same few techniques: * Explicit methods: cookies, link decoration, and other browser-supported ways of adding entropy. Browsers are working on removing these, but if they move too aggressively here then adtech just moves to: * Fingerprinting: using existing browser entropy. Generally worse than explicit methods because the user doesn't have control (ex: shared fingerprint between successive private browsing sessions). Browsers are also working on reducing this, see the article, but it's very hard because the number of techniques is large and they generally use features us
Read the rest
ers/sites depend on. * Timing attacks (pretty sure no one is doing this commercially yet) You might be interested in https://github.com/michaelkleber/privacy-model (Disclosure: I used to work on ads at Google)
In Protecting Against Browser-Language Fingerprinting
I think one thing overlooked is that Google's supposed rationale for providing this service is effectively because they suppose that their plans to "more aggressively block fingerprinting" will leave advertisers with no other choice. Personally I find this highly unlikely. The very nature of fingerprinting makes it difficult to prevent without some pretty severe compromises, and it wouldn't surprise me if advertisers enter an arms race with Google instead of caving in. Of course the economic strategy for Google to avoid that is to reduce the price/limits of this service to so low that this isn't worth doing, but if the effort Google puts into preventing fingerprinting is insufficent then this would lead to a "worst of both worlds" situation - Google gets to pseudonymously track the internet with their "privacy sandbox", and nefarious trac
Read the rest
kers/advertisers can combine that with fingerprinting to create an even more reliable picture of who's who on the Internet. FYI, this[0] appears to be the explainer of what Privacy Sandbox actually is, and it's quite vague, presumably because the actual implementation details of this would be difficult to determine. [0] https://github.com/michaelkleber/privacy-model
In Enter Sandbox: Google is building an internet without cookies
Interesting to me is that Google's Privacy Model suggestions of "Identity is partitioned by First Party Site" and "Third Parties can be allowed access to a first-party identity"[1] come off as more coherent and effective than Apple's ML based Tracking Prevention policies[2]. Issue is Google's third suggestion, "A per-first-party identity can only be associated with small amounts of cross-site information", is clearly advertiser-focused, not privacy-focused. I hope all can rally around the partitioning concepts and leave the others behind. [1]https://github.com/michaelkleber/privacy-model [2]https://webkit.org/blog/8828/intelligent-tracking-prevention...
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.