Hi Mike, Happy to give an update on each of these points:
Each API is continuing to make progress on draft specs. All early specifications have been published and each API is currently working on iterating on more recent changes based on feedback. - Attribution Reporting - https://wicg.github.io/attribution-reporting-api/ - Fenced Frames - https://wicg.github.io/fenced-frame/ - Fledge - https://wicg.github.io/turtledove/ - Private Aggregation - https://patcg-individual-drafts.github.io/private-aggregation-api/ - Shared Storage - https://wicg.github.io/shared-storage/ - Topics - https://patcg-individual-drafts.github.io/topics/ TAG review requests have been made for each of the API's, except for Private Aggregation which is a work in progress. - Topics- https://github.com/w3ctag/design-reviews/issues/726#issuecomment-1379908459 - Shared Storage - https://github.com/w3ctag/design-reviews/issues/747 - Fenced Frames- https://github.com/w3ctag/design-reviews/issues/735#issuecomment-1226822420 - FLEDGE - https://github.com/w3ctag/design-reviews/issues/723#issuecomment-1481081377 - ARA - https://github.com/w3ctag/design-reviews/issues/724 We are currently looking at re-filing / updating these requests to include recent changes, as some of these requests were made some time ago. bit.ly/blink-signals requests are ongoing and are expected to finish in the next couple of weeks. We have already started receiving feedback on some APIs. - Attribution Reporting & Fenced Frames - still in progress - Fledge: - Mozilla: https://github.com/mozilla/standards-positions/issues/770 - Webkit: https://github.com/WebKit/standards-positions/issues/158 - Private Aggregation - Private Aggregation is covered in both the Shared Storage and FLEDGE request. We have not requested separate vendor signals for Private Aggregation. - Shared Storage - Mozilla: https://github.com/mozilla/standards-positions/issues/646 - Webkit: https://github.com/WebKit/standards-positions/issues/10 - Topics - WebKit: https://github.com/WebKit/standards-positions/issues/111#issuecomment-1359609317 - Mozilla: https://github.com/mozilla/standards-positions/issues/622#issuecomment-1372979100 WPT tests are ongoing, many are completed with sufficient coverage. Private Aggregation has not begun yet. - Attribution Reporting- https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/wpt_internal/attribution-reporting/ - Fenced Frames - https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/wpt_internal/fenced_frame/ - Fledge- https://wpt.fyi/results/fledge?label=experimental&label=master&aligned - Shared Storage - https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/wpt_internal/shared_storage/?q=shared_storage%20wpt&ss=chromium - Topics - https://wpt.fyi/results/?label=master&label=experimental&aligned&q=topics If you have questions on specific areas here, let me know and I can provide any additional details/context. Thanks! On Thu, Apr 13, 2023 at 11:03 AM Mike Taylor <miketa...@chromium.org> wrote: > Hi John, > > Could you comment on any additional progress made in the 5 required areas > for OT extensions (see > https://www.chromium.org/blink/launching-features/#origin-trials)? > > thanks, > Mike > On 4/12/23 5:44 PM, John Delaney wrote: > > Greetings, > > We would like to extend the origin trial for all of the Privacy Sandbox > Ads APIs including: Topics, FLEDGE, Private Aggregation, Fenced Frames, > Attribution Reporting, and Shared Storage. > > We are sending a single intent for the extension because the rationale is > shared among the APIs. > > *Contact emails* > johni...@chromium.org, jkar...@chromium.org, pauljen...@chromium.org, > > *Explainer* > Attribution Reporting: > https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md and > https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md > > Fenced Frames: https://github.com/WICG/fenced-frame/tree/master/explainer > FLEDGE: https://github.com/WICG/turtledove/blob/master/FLEDGE.md > Shared Storage: https://github.com/WICG/shared-storage > Private Aggregation: > https://github.com/patcg-individual-drafts/private-aggregation-api > Topics API: > https://github.com/patcg-individual-drafts/topics/blob/main/README.md > > *Summary* > A collection of APIs to facilitate advertising: Attribution Reporting, > Fenced Frames, FLEDGE, Private Aggregation, Shared Storage and Topics. > > *Link to “Intent to Experiment” blink-dev discussion* > Attribution Reporting: > > https://groups.google.com/a/chromium.org/g/blink-dev/c/jEnNpideO1Y/m/nlEDdjmnCgAJ > Fenced Frames: > https://groups.google.com/a/chromium.org/g/blink-dev/c/y6G3cvKXjlg/m/DSNrBtxyAgAJ > FLEDGE: > > https://groups.google.com/a/chromium.org/g/blink-dev/c/0VmMSsDWsFg/m/_0T5qleqCgAJ > Private Aggregation: > https://groups.google.com/a/chromium.org/g/blink-dev/c/576sXtXNeCA > Shared Storage: > https://groups.google.com/a/chromium.org/g/blink-dev/c/jDx8z5a6ovk/m/H6w1UO-uBAAJ > Topics API: > https://groups.google.com/a/chromium.org/g/blink-dev/c/oTwd6VwCwqs/m/jPkW3T-mCgAJ > > > Unified OT Thread: > > https://groups.google.com/a/chromium.org/g/blink-dev/c/Vi-Rj37aZLs/m/wzeBWfxxEgAJ > > *Goals for experimentation* > Unchanged. > > *Experimental timeline* > We'd like to extend the origin trial for 3 additional milestones, with the > extension starting in 113 continuing through Chrome 115. The experiment is > therefore running from Chrome 101 through 115. We previously requested an > extension from Chrome 110 - 113 here > <https://groups.google.com/a/chromium.org/g/blink-dev/c/gpmaOi3of_w/m/SyMclFhMAAAJ> > . > > *Any risks when the experiment finishes?* > The unified origin trial is only available for a subset of Chrome users, > and requires developers to perform feature detection to use the APIs. > > *Reason this experiment is being extended* > We received feedback from developers resulting in the need for continued > testing and addressing several points of feedback that required changes to > the APIs. The extension will allow the ecosystem more time in stable > channels to continue their experiments. We additionally added individual > isolated experiments for each of the Privacy Sandbox APIs, an extension > will allow us to understand individual metrics outside of our existing > unified experiment > > These improvements include, but are not limited, to the following: > > Attribution Reporting > > - Various bug fixes & utility improvements > - Test cross app and web measurement > - Additional debugging capabilities including source success debug > reports > > <https://github.com/WICG/attribution-reporting-api/blob/main/verbose_debugging_reports.md#source-success> > > > Fenced Frames > > - Limited feedback so far > - FencedFrameConfig > > <https://github.com/WICG/fenced-frame/blob/master/explainer/fenced_frame_config.md> > API surface and supporting size for FLEDGE > <https://github.com/WICG/turtledove/pull/417> > - reportEvent dev tools support, support for ARA > > <https://github.com/WICG/turtledove/blob/main/Fenced_Frames_Ads_Reporting.md#support-for-attribution-reporting> > and for component ads > <https://github.com/WICG/turtledove/issues/332#issuecomment-1416224808> > > > FLEDGE > > - Improve latency (e.g. parallelization of FLEDGE auction support, > more timeout support, more latency reporting) > - Origin Trial Support (e.g. better integration with Private > Aggregation API, k-anonymity testing, misc features) > > > Private Aggregation (OT started in M107) > > - Adding support for a “context ID” to support report verification > within Shared Storage worklets > > > Shared Storage SelectURL > > - Replaced k-anon requirement with lower entropy limits during initial > phase > - Would like to have feedback from additional testers. > > > Topics > > - General utility improvements (filtering is less restrictive without > loss of privacy) > - Performance optimizations (topics can be sent via headers in fetch > and subframe navigation requests rather than creating an iframe and calling > javascript) > > > Feedback from the ecosystem will continue to influence the evolution of > the APIs. > > *Ongoing technical constraints* > Please see each API's initial Intent to Experiment. > > *Will this feature be supported on all five Blink platforms supported by > Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?* > Please see each API's initial Intent to Experiment. > > *Link to entry on the feature dashboard* > Attribution Reporting: https://chromestatus.com/feature/6412002824028160 > Fenced Frames: https://chromestatus.com/feature/5699388062040064 > FLEDGE: https://chromestatus.com/feature/5733583115255808 > Private Aggregation: https://chromestatus.com/feature/5743412790689792 > Shared Storage: https://chromestatus.com/feature/6256348582903808 > Topics: https://chromestatus.com/feature/5680923054964736 > > Unified Feature Dashboard: > https://chromestatus.com/feature/5100526168440832 > -- > 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/999f2f0a-9a90-47b0-9c3b-11ed6a8df1fen%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/999f2f0a-9a90-47b0-9c3b-11ed6a8df1fen%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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALW6VLyyqVSS6WVFAYAddE6TndTrEQkPivPAYFty77H_wW3RZQ%40mail.gmail.com.
