LGTM1

On Fri, Oct 20, 2023 at 9:44 AM Alex Turner <[email protected]> wrote:

> Contact emails
>
> [email protected]
>
> Explainer
> https://github.com/patcg-individual-drafts/private-aggregation-api#aggregation-coordinator-choice
> Specification
> https://github.com/patcg-individual-drafts/private-aggregation-api/pull/106
> Summary
>
> Modification to the Private Aggregation API to provide a mechanism for
> selecting which coordinator to use for payload encryption (from a
> vendor-specified allowlist). The choice of service is made with an
> additional option in Shared Storage’s run() and selectURL() calls, and in
> Protected Audience’s runAdAuction() and joinAdInterestGroup() calls. The
> broad approach largely aligns with Attribution Reporting’s approach (see
> https://chromestatus.com/feature/5197591256236032).
>
> Blink component
>
> Blink>PrivateAggregation
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPrivateAggregation>
>
> TAG review
>
> https://github.com/w3ctag/design-reviews/issues/846 (We have not
> requested a signal for these changes specifically.)
>
> TAG review status
>
> Pending
>
> Risks
>
> Interoperability and Compatibility
>
> This feature is optional and backwards compatible.
>
> Gecko: No signal (
> https://github.com/mozilla/standards-positions/issues/805) We have not
> requested a signal for these changes specifically. The Gecko position on
> Shared Storage (one of the ways Private Aggregation is exposed) is negative.
>
> WebKit: No signal (
> https://github.com/WebKit/standards-positions/issues/189) We have not
> requested a signal for these changes specifically.
>
> Web developers: No signals
>
> Other signals:
>
> WebView application risks
>
> Does this intent deprecate or change behavior of existing APIs, such that
> it has potentially high risk for Android WebView-based applications?
>
> None
>
>
> Debuggability
>
> No new debug capabilities beyond the existing internals page
> (chrome://private-aggregation-internals) and temporary debug mode.
>
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, Chrome OS, Android, and Android WebView)?
>
> All but Webview
>
>
> Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
> ?
>
> WPTs will be added when the feature is enabled.
>
> Flag name on chrome://flags
>
> None
>
> Finch feature name
>
> PrivateAggregationApiMultipleCloudProviders
>
> Requires code in //chrome?
>
> False
>
> Tracking bug
>
> https://crbug.com/1481761
>
> Launch bug
>
> https://launch.corp.google.com/launch/4272421
>
> Estimated milestones
>
> We intend to ship in M120.
>
> Anticipated spec changes
>
> None
>
> Link to entry on the Chrome Platform Status
>
> https://chromestatus.com/feature/5140711678935040
>
> Links to previous Intent discussions
>
> Original I2S
> <https://groups.google.com/a/chromium.org/g/blink-dev/c/8cKaLstq2QQ/m/Udrbb4ifDQAJ>,
> Follow-up enhancements I2S
> <https://groups.google.com/a/chromium.org/g/blink-dev/c/cNK_uuCaNMs/m/spuk_w4nAAAJ>
>
>
> This intent message was generated by Chrome Platform Status
> <https://chromestatus.com/>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA%2BBiFmJSK39%3D%3DRoWBmxnmZ2Y3h4krDKFBa_CUHAH%2BzjXj-T3A%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA%2BBiFmJSK39%3D%3DRoWBmxnmZ2Y3h4krDKFBa_CUHAH%2BzjXj-T3A%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_P9BF5jKV9%3DFLY4CfJXHy%2BiCR%2Bofg6gMS%3DLDcbUDxkVw%40mail.gmail.com.

Reply via email to