Skip to content

Some followup changes regarding epochs #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
May 19, 2025
Merged

Some followup changes regarding epochs #126

merged 10 commits into from
May 19, 2025

Conversation

martinthomson
Copy link
Member

@martinthomson martinthomson commented Apr 3, 2025

Looking at @csharrison here for a review.

I threw in a fix for #125 with this as a bonus.


Preview | Diff

but retaining browsing history,
a [=user agent=] can [=map/set=] the value
in the [=privacy budget store=] to 0 for all [=epochs=]
for all affected [=sites=].

When clearing site data at the request of a [=site=],
through the use of the [:Clear-Site-Data:] header,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to address the points from #125 (comment)?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that the discussion there suggests - to me at least - that we need to keep that issue open and do a little more work. This is probably enough for now, given that.

@apasel422 apasel422 requested a review from csharrison April 4, 2025 12:11
@martinthomson martinthomson merged commit b26b200 into main May 19, 2025
1 check failed
@martinthomson martinthomson deleted the epoch-followup branch May 19, 2025 05:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants