-
Notifications
You must be signed in to change notification settings - Fork 35
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
Add details about server orchestrated multi seller flow for PAS auctions #184
Conversation
encrypted Protected Audience request payload. The top-level seller’s code in the publisher web page asks the browser | ||
for this encrypted Protected Audience data to include in the unified request. | ||
encrypted Protected Audience request payload. The top-level seller’s code in the publisher web page/app asks the browser/android API | ||
for the encrypted Protected Audience/Protected App Signals data to include in the unified request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we instead do the following here:
s@Protected Audience/Protected App Signals@Protected Auction(Protected Audience OR Protected App Signals)@
and then use Protected Audience everywhere else below?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It sounds good to me, but does have the risk of adding a new term in the middle of the explainer. Have we used Protected Auction in other explainers to refer to both as a group?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we do use Protected Auction to cover both- https://github.com/privacysandbox/protected-auction-services-docs/blob/main/bidding_auction_services_api.md#bidding-and-auction-services
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good. will update today.
Add the Model Freezing section.
* correct cpu metric as one metric with different labels * fix error * Update monitoring_protected_audience_api_services.md
More points of clarification regarding trusted Key/Value requirements for Android
* Add explainer for experiment with randomly split traffic * update pr
* Add FAQ for UDF log * Update debugging_protected_audience_api_services.md
* Add the cost estimation tool explainer and update the main explainer
* Create b&a-kanon-integration.md * Update b&a-kanon-integration.md * Rename b&a-kanon-integration.md to bidding-auction-services-kanon-integration.md * Update bidding-auction-services-kanon-integration.md * Update bidding-auction-services-kanon-integration.md
Index missing explainers
* Update monitoring_protected_audience_api_services.md
…ures" section to clarify that B&A services currently only support the amd64 architecture (x86_64 ISA). (#216)
Add PV section to system design explainer
NsJail is the default sandbox
No description provided.