HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
WICG
privacy-preserving-ads
HCL2021–2021
WICG / privacy-preserving-ads

privacy-preserving-ads

Privacy-Preserving Ads

4Distinct people
9Mentions
0Explicit recommenders
106GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Privacy-Preserving Ads

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, 5:04:57 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 week9 dated mentions

Observed mentions: 2021-04-18 18:14:56 UTC to 2021-07-13 19:32:53 UTC. Weeks start Monday, UTC.

0122021-04-12 00:00:00 UTC to 2021-04-19 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsApr 122021-04-19 00:00:00 UTC to 2021-04-26 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2021-04-26 00:00:00 UTC to 2021-05-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-05-03 00:00:00 UTC to 2021-05-10 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-05-10 00:00:00 UTC to 2021-05-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-05-17 00:00:00 UTC to 2021-05-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-05-24 00:00:00 UTC to 2021-05-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 242021-05-31 00:00:00 UTC to 2021-06-07 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-06-07 00:00:00 UTC to 2021-06-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-06-14 00:00:00 UTC to 2021-06-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-06-21 00:00:00 UTC to 2021-06-28 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-06-28 00:00:00 UTC to 2021-07-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-05 00:00:00 UTC to 2021-07-12 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-07-12 00:00:00 UTC to 2021-07-19 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 12

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
Apr 122021-04-12 00:00:00 UTC2021-04-19 00:00:00 UTC202
Apr 192021-04-19 00:00:00 UTC2021-04-26 00:00:00 UTC220
Apr 262021-04-26 00:00:00 UTC2021-05-03 00:00:00 UTC000
May 32021-05-03 00:00:00 UTC2021-05-10 00:00:00 UTC101
May 102021-05-10 00:00:00 UTC2021-05-17 00:00:00 UTC000
May 172021-05-17 00:00:00 UTC2021-05-24 00:00:00 UTC000
May 242021-05-24 00:00:00 UTC2021-05-31 00:00:00 UTC000
May 312021-05-31 00:00:00 UTC2021-06-07 00:00:00 UTC101
Jun 72021-06-07 00:00:00 UTC2021-06-14 00:00:00 UTC000
Jun 142021-06-14 00:00:00 UTC2021-06-21 00:00:00 UTC000
Jun 212021-06-21 00:00:00 UTC2021-06-28 00:00:00 UTC101
Jun 282021-06-28 00:00:00 UTC2021-07-05 00:00:00 UTC000
Jul 52021-07-05 00:00:00 UTC2021-07-12 00:00:00 UTC101
Jul 122021-07-12 00:00:00 UTC2021-07-19 00:00:00 UTC101

What Hacker News says

9 sources
> Google's position is ... Everyone else's position is... I don't think this categorization is accurate. For example, Apple built https://webkit.org/blog/8943/privacy-preserving-ad-click-att... > if the data isn't required to operate, you don't need it This is simple, but it's also wrong. Some counterexamples: * Learning from implicit feedback: dictation software can operate without learning what corrections people make, or a search engine can operate without learning what links people click on, but the overall quality will be lower. Each individual piece of information isn't required, but the feedback loop allows building a substantially better product. * Risk-based authentication: you have various ways to identify a user, some of which are more hassle for them than others. A login cookie is lowest friction, asking for a password add
Read the rest
s more friction, email / SMS / OTP verification add even more. You don't want to ask all users to go through the highest-friction approach on every pageview, but you also don't want to let a fraudster who gets access to someone's cookiejar/leaked password/old device/etc impersonate the user. If you have a small amount of information about the current user's browsing environment, in a way that's hard for a fraudster to imitate, you can offer much lower friction for a given level of security. * Incremental rollouts: when you make changes to software that operates in complex environments it can be very difficult to ensure that it operates correctly through testing alone. Incremental rollouts, with telemetry to verify that there are no regressions or that relevant bugs have been fixed, produces better software. You're writing as if your position is Firefox's but even they collect telemetry by default: https://support.mozilla.org/en-US/kb/telemetry-clientid > the position of every non-Google-browser is that they want to give sites as close to no data at all as possible ... Every single browser developer that doesn't own an Ads and Analytics suite is opposed to Privacy Sandbox. I cited Apple's conversion tracking API above, but another example of this general approach is Microsoft's https://github.com/WICG/privacy-preserving-ads/blob/main/Par... I don't know where you're getting that they're trying for "close to no data at all", as opposed to improving privacy and preventing cross-site tracking? (Still speaking only for myself)
In Downgrade User Agent Client Hints to 'harmful'
Why don't you think the browsers can agree on replacements? Most of the major browsers have proposals for replacing some piece of advertising-related third party cookies [1][2][3]. (Disclosure: I work on ads at Google, speaking only for myself) [1] Safari: https://github.com/privacycg/private-click-measurement [2] Edge: https://github.com/WICG/privacy-preserving-ads/blob/main/Par... [3] Chrome: https://www.chromium.org/Home/chromium-privacy/privacy-sandb...
In Google extends third party cookie deadline until late 2023
Chrome's FLoC and TURTLEDOVE proposals are nascent web standards under the Web Incubator Community Group (https://wicg.io). My understanding is that Chrome is hoping to come up with something that other browsers also like? Other browsers are working on this general project ("how do you do ads without cookies") too: Edge has https://github.com/WICG/privacy-preserving-ads/blob/main/Par... and Safari has https://webkit.org/blog/8943/privacy-preserving-ad-click-att...
In Apple, FedEx and the cookie apocalypse

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.