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

Spec: Define per-calling-API limit on contributions per report #150

Conversation

dmcardle
Copy link
Contributor

@dmcardle dmcardle commented Jul 26, 2024

This PR corresponds to

Note that this PR depends on #149. (GitHub doesn't understand dependent PRs, so this appears to include its parent's changes.)


Preview | Diff

@dmcardle
Copy link
Contributor Author

@alexmturner PTAL :)

(Yay, CI gave me a green checkmark because I rebased on #149.)

@dmcardle dmcardle changed the title Spec: Define per-API limit on contributions per report Spec: Define per-calling-API limit on contributions per report Jul 26, 2024
Copy link
Collaborator

@alexmturner alexmturner left a comment

Choose a reason for hiding this comment

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

Generally LG! One layering question that might need some discussion

spec.bs Outdated Show resolved Hide resolved
spec.bs Outdated Show resolved Hide resolved
spec.bs Show resolved Hide resolved
@dmcardle dmcardle force-pushed the dmcardle-protected-audience-100-contribs-spec branch 2 times, most recently from ee9f46d to 0eba66b Compare August 6, 2024 18:15
alexmturner pushed a commit that referenced this pull request Aug 23, 2024
Modifies the explainer to mention that these limits can be different per-API and to list the planned implementaiton plan (i.e. increasing Protected Audience's limit to 100). For more detail, see #81 (comment).

Related spec change: #150
aarongable pushed a commit to chromium/chromium that referenced this pull request Aug 27, 2024
This CL implements the logic for limiting Protected Audience callers to
100 contributions per report. Shared Storage callers are not affected.

The new behavior is gated behind a feature flag that is disabled by
default.

* Explainer change:
  patcg-individual-drafts/private-aggregation-api#138

* Spec change:
  patcg-individual-drafts/private-aggregation-api#150

Bug: 360160864
Change-Id: I14cd4087986a8ecb70e60701d56fac6d25135a53
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5743397
Commit-Queue: Dan McArdle <[email protected]>
Reviewed-by: Alex Turner <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1347486}
spec.bs Outdated Show resolved Hide resolved
Copy link
Collaborator

@alexmturner alexmturner left a comment

Choose a reason for hiding this comment

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

LGTM w one more nit

@dmcardle dmcardle force-pushed the dmcardle-protected-audience-100-contribs-spec branch from 0eba66b to 5c54351 Compare September 3, 2024 16:14
@alexmturner alexmturner merged commit 419c30e into patcg-individual-drafts:main Sep 3, 2024
1 check passed
github-actions bot added a commit that referenced this pull request Sep 3, 2024
SHA: 419c30e
Reason: push, by alexmturner

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@dmcardle dmcardle deleted the dmcardle-protected-audience-100-contribs-spec branch September 3, 2024 17:28
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.

2 participants