> Please fill out and start the reviews for Privacy, Security and Debuggability in your chromestatus entry, thanks. These are all in review now. Sorry, I forgot about this new step.
> Can you clarify what the proposed end milestone will be? I hope the Origin Trial to last M119 through M121, though I strongly suspect I'll need to extend this further to provide sufficient time to test. On Wed, Oct 18, 2023 at 12:04 PM Mike Taylor <miketa...@chromium.org> wrote: > Hi Paul, > > Can you clarify what the proposed end milestone will be? > > thanks, > Mike > On 10/13/23 10:46 AM, Chris Harrelson wrote: > > Please fill out and start the reviews for Privacy, Security and > Debuggability in your chromestatus entry, thanks. > > On Thu, Oct 12, 2023 at 3:40 PM Paul Jensen <pauljen...@chromium.org> > wrote: > >> Contact emails >> >> pauljen...@chromium.org, behamil...@google.com >> >> Explainer >> >> Chrome: >> https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md >> >> Services: >> https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md >> >> Note that this explainer has a helpful onboarding section >> <https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md#onboarding-and-alpha-testing-guide> >> for setting up the services. >> >> Specification >> >> May be influenced by Origin Trial feedback, so not yet started. >> Protected Audience auctions running on Bidding & Auction Services provide >> functionality very similar to existing on-device auctions so much of the >> existing spec <https://wicg.github.io/turtledove/> applies. >> >> Summary >> >> The Protected Audience API (formerly known as FLEDGE) is a Privacy >> Sandbox proposal to serve remarketing and custom audience use cases, >> designed so third parties cannot track user browsing behavior across sites. >> This proposal, the Protected Audience Bidding & Auction Services proposal, >> outlines a way to allow Protected Audience computation to take place on >> cloud servers in a Trusted Execution Environment (TEE), rather than running >> locally on a user's device. Moving computation to cloud servers can help >> optimize the Protected Audience auction, and free up computational cycles >> and network bandwidth for a device. >> >> Blink component >> >> Blink>InterestGroups >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EInterestGroups> >> >> TAG review >> >> The parent proposal, Protected Audience, is still pending: >> https://github.com/w3ctag/design-reviews/issues/723 >> >> TAG review status >> >> Pending >> >> Risks Interoperability and Compatibility >> >> None. This is an optional new feature of the Protected Audience API. Ad >> techs can use this new feature by calling >> navigator.getInterestGroupAdAuctionData() and specifying values for new >> fields in the auction config. Without invoking the new function or explicit >> values for those new fields, there's no functional behavioral change as a >> result of this feature. >> >> Gecko & WebKit: No signal on parent proposal, Protected Audience. Asked >> in the Mozilla forum here >> <https://github.com/mozilla/standards-positions/issues/770>, and in the >> Webkit forum here >> <https://github.com/WebKit/standards-positions/issues/158>. >> >> Web developers: Extensive interest in this feature from adtechs, >> evidenced by the myriad of discussions on Protected Audience’s issue >> tracker <https://github.com/WICG/turtledove/issues> and weekly WICG calls >> <https://github.com/WICG/turtledove/issues/88>. >> >> Goals for experimentation >> >> Operating Bidding and Auction services in TEEs represents a major shift >> from running Protected Audience auctions inside the browser. During this >> Origin Trial we’d like to gain confidence that this is possible to do at >> scale and in a performant manner. We want feedback on new API surfaces and >> how these servers are operated. >> >> Debuggability >> >> On-device API surfaces should be debuggable in Chrome DevTools, and we’ve >> added extensive mechanisms for debugging Bidding and Auction services >> <https://github.com/privacysandbox/fledge-docs/blob/main/debugging_protected_audience_api_services.md> >> . >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, 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> >> ? >> >> No. More web-platform-test >> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >> coverage is expected when the specification is closer to completion. >> >> Flag name on chrome://flags >> >> Overall control is not possible via chrome://flags, though the consented >> debugging support >> <https://github.com/privacysandbox/fledge-docs/blob/main/debugging_protected_audience_api_services.md#adtech-consented-debugging> >> is controlled via chrome://flags/#protected-audience-debug-token >> >> Finch feature name >> >> FledgeBiddingAndAuctionServerAPI >> >> Requires code in //chrome? >> >> Only for UI for the consented debugging support >> <https://github.com/privacysandbox/fledge-docs/blob/main/debugging_protected_audience_api_services.md#adtech-consented-debugging> >> . >> >> Estimated milestones >> >> We hope to start the Origin Trial sometime during M119 beta. We plan to >> continue the Origin Trial for at least three milestones to give developers >> time to test the API and provide feedback. Once we are confident that the >> APIs are working properly, we will transition the OT from beta to stable >> channel. >> >> Link to entry on the Chrome Platform Status >> >> https://chromestatus.com/feature/4649601971257344 >> >> Links to previous Intent discussions >> >> Intent to prototype: >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrnSdvf7RgK2wxsmC6rWc8eRoqDZOvgwVFuEx1r2nqmAJg%40mail.gmail.com >> >> 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 on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWr%3D7Cfcv00pao_rDJeT2-67jfRNzk%2BgTHQ13eCUyguPcfA%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWr%3D7Cfcv00pao_rDJeT2-67jfRNzk%2BgTHQ13eCUyguPcfA%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 on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-ZqmTS%2BDKxa9UQsiHR2G%3DvCr2srSOR%3Da6ucU2bYrT11w%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-ZqmTS%2BDKxa9UQsiHR2G%3DvCr2srSOR%3Da6ucU2bYrT11w%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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrk45RHWA4nyB5164zgd0kf%2Be6Y_cu0mrhDcn6vdo1rEUw%40mail.gmail.com.
