Skip to content
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

Remove aggregatable report limit when trigger context ID is non-null #1475

Merged
merged 7 commits into from
Jan 10, 2025

Conversation

giladbarkan-github
Copy link
Collaborator

@giladbarkan-github giladbarkan-github commented Dec 6, 2024

The current hard limit on aggregatable reports per source might be too small for
some use-cases. Allowing consumers to manage report counts that already have
privacy constraints applied provides more flexibility. In the case of this
change, when a trigger context ID is supplied, null report rate already manages
the necessary privacy constraints in place of a hard limit on aggregatable
report count.

(See also #1183)


Preview | Diff

@linnan-github
Copy link
Collaborator

@giladbarkan-github
Copy link
Collaborator Author

@arpanah arpanah self-requested a review December 13, 2024 19:17
AGGREGATE.md Show resolved Hide resolved
Copy link
Contributor

@johnivdel johnivdel left a comment

Choose a reason for hiding this comment

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

lgtm

@akashnadan akashnadan merged commit 51fa4ec into WICG:main Jan 10, 2025
2 checks passed
aarongable pushed a commit to chromium/chromium that referenced this pull request Jan 21, 2025
WICG/attribution-reporting-api#1475

Bug: 389733591
Change-Id: Ic74cbb00d484112e35edbe40980e6d401f5c6976
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6106647
Commit-Queue: Andrew Paseltiner <[email protected]>
Reviewed-by: Nan Lin <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1409200}
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.

7 participants