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

turtledove

TURTLEDOVE

18Distinct people
39Mentions
0Explicit recommenders
588GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

TURTLEDOVE

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

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, 3:44:08 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 year39 dated mentions

Observed mentions: 2020-03-25 01:04:40 UTC to 2023-10-30 21:42:16 UTC.

05101520252020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 25 mentions; 0 submissions, 25 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2023

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 UTC826
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC25025
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 UTC615

What Hacker News says

8 sources
One of the most common cases of targeting ads is remarketing: someone comes to your site, they start the process of buying a tablesaw but then leave for whatever reason. You pay to show ads of the saw so they can come back and finish their purchase if they want to. Traditionally, this has been implemented with third party cookies. The retailer drops a cookie on the users browser, and then buys ads to be shown to anyone matching that cookie. I don't know if I would call this data mining, but it is certainly not private. It is possible to build a system that supports remarketing in a private way, however, with new browser APIs: https://github.com/WICG/turtledove (Disclosure: I work on ads at Google, speaking only for myself)
In Apple’s Anti-Tracking Plans for iPhone
Who tags though, publishers? I mean, you're right; I'm not being a contrarian for the sake of argument. Contextual targeting probably will have a more interesting pitch in a post-third-party cookie Internet, but it's not going to be _the_ solution. There are already proposals for targeted advertising that may be more compelling/cheaper-to-implement, see TURTLEDOVE: https://github.com/WICG/turtledove.
In Dutch national broadcaster saw ad revenue rise when it stopped tracking users
Ad personalization can be handled by the ad network. The network contract they are interested in buying a car, and Fiat can request their ads be shown to people interested in buying a car. Fiat only learns that you are in the "people interested in buying a car" category if they win the bidding to show you an ad. Not great, since showing an ad, especially well out of the viewport, is pretty cheap. We can take this one step further with the proposed TURTLEDOV browser API (https://github.com/michaelkleber/turtledove), at which point the ad network doesn't learn your interests and Fiat only learns you were interested in buying a car if you click on an ad. Or with the proposed FLoC browser API (https://github.com/jkarlin/floc) where your browser uses on-device clustering to present an interest category instead of the ad network learning inte
Read the rest
rests server-side. (Disclosure: I work on ads at Google, and am friends with the folks behind these proposals)
In Oracle’s BlueKai tracks people across the web – that data spilled online
My parent comment wasn't arguing for privacy, they were arguing against personalization. Specifically, I referenced two proposals for privacy-preserving ad personalization, FLoC (https://github.com/jkarlin/floc) and TURTLE-DOV (https://github.com/michaelkleber/turtledove), and their response was that privacy wasn't the issue, the effects of personalization are harmful in themselves. For privacy I do agree that you can't just do it with legislation and you also need technology. But if you think the issue is personalization itself, regardless of how privately it is implemented, then legislation is the critical playing field. Blocking personalization on the open web through technical means while allowing it in walled gardens means you (a) still have most of the claimed harms of personalization but also (b) massively disadvantage the open w
Read the rest
eb.
In Full third-party cookie blocking and more
I'm confused why you would say both that browsers should block all ads by default and that most forms of advertising are totally fine? > I’m even favor of targeted advertising so long as it’s targeted to the content demographics instead the literal individual following them around Then you might like FLoC (https://github.com/jkarlin/floc) and TURTLE-DOV (https://github.com/michaelkleber/turtledove). These are both ways of implementing targeted advertising without letting the advertiser or ad network follow you around.
In Full third-party cookie blocking and more

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.