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: export obtain the Private Aggregation coordinator algorithm #163

Merged
merged 2 commits into from
Oct 18, 2024

Conversation

alexmturner
Copy link
Collaborator

@alexmturner alexmturner commented Oct 14, 2024

The version that takes a USVString is shared between Protected Audience and Shared Storage, so we can export it. Updates links so that the monkey patched version has a modified linking text as that will be removed from this spec soon.


Preview | Diff

The version that takes a USVString is shared between Protected Audience
and Shared Storage, so we can export it. Updates links so that the
monkey patched version has a modified linking text as that will be
removed from this spec soon.
Copy link

@qingxinwu qingxinwu left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks

spec.bs Outdated
@@ -2119,37 +2138,18 @@ They return an [=interest group=] or null:
</div>

<div algorithm>
To <dfn>obtain the Private Aggregation coordinator</dfn> given a
To <dfn lt="obtain the Private Aggregation coordinator from a PA config">obtain
the Private Aggregation coordinator</dfn> given a

Choose a reason for hiding this comment

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

nit: is there a reason to keep this the same name as the other? Is it slightly easier to just call it "... from a PA config"

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I was treating them like "overloaded" functions, but I don't feel strongly. That being said, I don't love the "PA config" if it's the proper name -- maybe we could call it "obtain the coordinator from a Private Aggregation config"?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Went with this!

Choose a reason for hiding this comment

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

LGTM

@alexmturner
Copy link
Collaborator Author

Thanks!

@alexmturner alexmturner merged commit d98b3fc into main Oct 18, 2024
1 check passed
@alexmturner alexmturner deleted the pa_coordinator_algo branch October 18, 2024 15:02
github-actions bot added a commit that referenced this pull request Oct 18, 2024
SHA: d98b3fc
Reason: push, by alexmturner

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot added a commit to morlovich/private-aggregation-api that referenced this pull request Oct 21, 2024
…tcg-individual-drafts#163)

SHA: d98b3fc
Reason: push, by morlovich

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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