LGTM to experiment On Fri, Mar 25, 2022 at 10:31 PM Josh Karlin <jkar...@chromium.org> wrote:
> Contact emails > > yao...@chromium.org, jkar...@chromium.org > > Developers interested in the Topics API can also join the Topics API > announcements > <https://groups.google.com/a/chromium.org/g/topics-api-announce> group > for updates and announcements. > > Explainer > > https://github.com/jkarlin/topics > > Specification > > TBD > > Summary > > The intent of the Topics API is to provide callers (including third-party > ad-tech or advertising providers on the page that run script) with > coarse-grained advertising topics that the page visitor might currently be > interested in. These topics will supplement the contextual signals from the > current page and can be combined to help find an appropriate advertisement > for the visitor. > > > Blink component > > Blink>InterestCohort > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EInterestCohort> > > Search tags > > Topics <https://chromestatus.com/features#tags:Topics>, browsingTopics > <https://chromestatus.com/features#tags:browsingTopics>, FLoC > <https://chromestatus.com/features#tags:FLoC> > > TAG request > > https://github.com/w3ctag/design-reviews/issues/726 > > Risks > Interoperability and Compatibility > > Gecko: issue <https://github.com/mozilla/standards-positions/issues/622> > – requested March 17th 2022 > > WebKit: webkit-dev thread > <https://lists.webkit.org/pipermail/webkit-dev/2022-March/032159.html> – > requested March 17th 2022 > > Web developers: Lots of interest in issues in the explainer. Concerns > center around utility. Balancing privacy/utility and making tweaks to the > algorithms so that we get this right is what the OT is all about. > > 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? > > No > > > Goals for experimentation > > The intent is for experimenters to try Topics out and see how it performs > for them. We expect there to be bumps along the road toward optimizing > privacy and utility trade-offs. We also expect it may be necessary to > change parameters and algorithms along the way (e.g., we’re already having > discussions around adding Topics in request headers and weighting topics by > frequency). So please experiment and provide feedback on the issue tracker > <https://github.com/jkarlin/topics/issues> to help us improve it. > > Experiment Configuration > > The origin trial for this experiment will be shared among various Privacy > Sandbox APIs. Our goal is to allow for coordinated experiments to be run by > multiple different sites, across multiple APIs in one OT. > > This shared origin trial, Privacy Sandbox Ads APIs, will be a third-party > origin trial. To ensure that developers can run coordinated experiments > without concern for exceeding page load usage thresholds, this Origin Trial > will be available for a subset of users by default. Therefore, it will be > necessary to feature test to ensure that the API surface you want to use is > available after providing your OT token. A second advantage of this > configuration is that different experimenters will experiment with the same > users, which enables coordination for APIs like FLEDGE across third parties. > > > > Reason this experiment is being extended > > N/A > > Ongoing technical constraints > > Debuggability > > There are no particular debugging APIs made available or dev-tools > integrations for this OT. > > > 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/+/master/docs/testing/web_platform_tests.md> > ? > > Not yet, but those tests are coming. > > Flag name > > privacy-sandbox-ads-apis > > Requires code in //chrome? > > False > > Launch bug > > https://bugs.chromium.org/p/chromium/issues/detail?id=1286877 > > Estimated milestones > > We hope to start the Origin Trial sometime during M101 beta. We plan to > continue the Origin Trial until at least M104 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/5680923054964736 > > Links to previous Intent discussions > > Intent to prototype: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b845db21-f158-4bf3-9109-7f4665126ec1n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b845db21-f158-4bf3-9109-7f4665126e...@chromium.org> > > > 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/CAANMuaNXE3KYymq%3Dd0jcOmw%2Br2si_DOJK4cc%2BqMCU8mCoQBWTA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAANMuaNXE3KYymq%3Dd0jcOmw%2Br2si_DOJK4cc%2BqMCU8mCoQBWTA%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/CAARdPYcMo-Em450YMBRPzGtXCxTAYjbFpUvC5_V8ZAqDbARzEw%40mail.gmail.com.
