LGTM2 On Fri, Jan 17, 2025 at 10:15 AM Mike Taylor <miketa...@chromium.org> wrote:
> I see the WPTs have all landed now, thanks. > > LGTM1 > On 1/16/25 2:16 PM, Qingxin Wu wrote: > > https://crrev.com/c/6179638 is the CL that's work in progress, but I hope > to submit it soon. > > > > On Thu, Jan 16, 2025 at 12:03 PM Mike Taylor <miketa...@chromium.org> > wrote: > >> Thanks Paul. Do we have a CL up for forDebuggingOnly that I can subscribe >> to? >> On 1/14/25 8:20 AM, Paul Jensen wrote: >> >> The Private Aggregation ones landed here >> <https://chromium-review.googlesource.com/c/chromium/src/+/6164350>. >> The downsampled forDebugginOnly ones are in progress. >> >> On Wed, Dec 18, 2024 at 4:12 PM Mike Taylor <miketa...@chromium.org> >> wrote: >> >>> Can you let us know when you have landed WPTs? >>> On 12/17/24 3:44 PM, Paul Jensen wrote: >>> >>> Contact emails >>> >>> pauljen...@chromium.org >>> >>> qingxi...@google.com >>> >>> >>> Explainer >>> >>> For original Protected Audience Private Aggregation reporting support: >>> https://github.com/WICG/turtledove/pull/386 >>> >>> For original Protected Audience downsampling forDebuggingOnly reporting: >>> https://github.com/WICG/turtledove/pull/1020 >>> >>> >>> Specification >>> >>> Private aggregation reporting: >>> >>> - >>> >>> Web spec: https://github.com/WICG/turtledove/pull/1344 >>> - >>> >>> Protocol spec: >>> >>> https://github.com/privacysandbox/draft-ietf-bidding-and-auction-services/pull/15 >>> >>> >>> Downsampling fDO: >>> >>> - >>> >>> Web spec: https://github.com/WICG/turtledove/pull/1325 >>> - >>> >>> Protocol spec: >>> >>> https://github.com/privacysandbox/draft-ietf-bidding-and-auction-services/pull/17 >>> >>> >>> Summary >>> >>> This feature adds changes necessary in Chrome to support two reporting >>> mechanisms for Protected Audience (PA) auctions run on Bidding and >>> Auction Services (B&A) >>> <https://github.com/privacysandbox/protected-auction-services-docs/blob/main/bidding_auction_services_api.md> >>> : >>> >>> 1. >>> >>> Private Aggregation Reporting: for measuring aggregate, cross-site >>> data in a privacy preserving manner. >>> 2. >>> >>> Downsampling of forDebuggingOnly (fDO) reports: changes necessary in >>> the client to support the eventual implementation of downsampling of fDO >>> in >>> B&A. Chrome previously supported these reporting mechanisms for on-device >>> PA auctions, and this feature brings them to B&A on-server auctions. >>> >>> >>> Blink component >>> >>> Blink>InterestGroups >>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EInterestGroups> >>> >>> >>> TAG review >>> >>> For Protected Audience: >>> https://github.com/w3ctag/design-reviews/issues/723 >>> >>> For Protected Audience Bidding and Auction Services: >>> https://github.com/w3ctag/design-reviews/issues/1009 >>> >>> >>> TAG review status >>> >>> Completed for Protected Audience, resolved unsatisfied. >>> >>> >>> Risks Interoperability and Compatibility >>> >>> Feature represents optional new behavior that shouldn’t break existing >>> usage. >>> >>> >>> Gecko & WebKit: For Protected Audiences in general - Negative from >>> Mozilla >>> <https://github.com/mozilla/standards-positions/issues/770#issuecomment-2432124085>. >>> No signal from Webkit >>> <https://github.com/WebKit/standards-positions/issues/158#issuecomment-2432121278> >>> . >>> >>> >>> Edge: Edge is running an Origin Trial of the Ad Selection API >>> <https://github.com/WICG/privacy-preserving-ads/blob/main/README.md> >>> which shares a Web API and services protocol with PA. Their auction >>> reporting doc >>> <https://github.com/WICG/privacy-preserving-ads/blob/main/Auction%20Reporting.md> >>> says future work includes aggregate reporting which can be facilitated by >>> this. >>> >>> >>> Web developers: >>> >>> Private aggregation reporting in Protected Audience: Discussed on github >>> (1 <https://github.com/WICG/turtledove/issues/164>, 2 >>> <https://github.com/WICG/turtledove/issues/16>, 3 >>> <https://github.com/WICG/turtledove/issues/54>, 4 >>> <https://github.com/WICG/turtledove/issues/289>, 5 >>> <https://github.com/patcg-individual-drafts/private-aggregation-api/issues/12> >>> ). >>> >>> Downsampled forDebuggingOnly in Protected Audience: Discussed here >>> <https://github.com/WICG/turtledove/issues/632> and in person here >>> <https://github.com/WICG/turtledove/blob/main/meetings/2024-01-17-FLEDGE-call-minutes.md#:~:text=on%20the%20URL.-,forDebuggingOnly%20availability,-%2D%20%23632> >>> . >>> >>> >>> Debuggability >>> >>> On-device API surfaces should be debuggable in Chrome DevTools, and >>> we’ve added extensive mechanisms for debugging >>> <https://github.com/privacysandbox/fledge-docs/blob/main/debugging_protected_audience_api_services.md> >>> Bidding >>> and Auction services >>> <https://github.com/privacysandbox/protected-auction-services-docs/blob/main/bidding_auction_services_api.md#related-documents> >>> . >>> >>> >>> Will this feature be supported on all six Blink platforms (Windows, Mac, >>> Linux, ChromeOS, Android, and Android WebView)? >>> >>> It will be supported on all platforms that support Protected Audience, >>> so 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> >>> ? >>> >>> We plan to add WPTs to cover this API shortly. We already have WPTs for >>> Protected Audience Bidding and Auction Services and for Protected Audience >>> private aggregation reporting, and will extend these accordingly. >>> >>> >>> Flag name on chrome://flags >>> >>> None >>> >>> >>> Finch feature name >>> >>> EnableBandAPrivateAggregation, >>> >>> EnableBandASampleDebugReports >>> >>> >>> Requires code in //chrome? >>> >>> False >>> >>> >>> Estimated milestones >>> >>> Shipping on desktop and Android in M132. >>> >>> >>> Anticipated spec changes >>> >>> None >>> >>> >>> Link to entry on the Chrome Platform Status >>> >>> https://chromestatus.com/feature/5150193518116864 >>> >>> >>> 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 blink-dev+unsubscr...@chromium.org. >>> To view this discussion visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWr%3DAvniF65_Md9iEt_Ws6jML20b7XSu0S8utViDSan3p8g%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWr%3DAvniF65_Md9iEt_Ws6jML20b7XSu0S8utViDSan3p8g%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 blink-dev+unsubscr...@chromium.org. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fbe85527-d6d1-49a5-8563-763e334d5f57%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fbe85527-d6d1-49a5-8563-763e334d5f57%40chromium.org?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 blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-357_Dkb_yys%2BqRpci9_onFU8_qHDTU%2BN%3DMTaYHRUFjQ%40mail.gmail.com.
