Re: [blink-dev] Intent to Ship (I2S): Protected Audience

LGTM2 On Thu, Jul 6, 2023, 11:54 AM Rick Byers wrote: > Protected audiences seems like one of the most powerful and complex > features ever added to Chromium, and I'll admit I've struggled to > understand it at enough depth to do a decent API owner review. I carved out > a few more hours this

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

Protected audiences seems like one of the most powerful and complex features ever added to Chromium, and I'll admit I've struggled to understand it at enough depth to do a decent API owner review. I carved out a few more hours this morning and am now comfortable giving my LGTM1 to ship. My

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

On Fri, Jun 30, 2023 at 5:03 PM Mike Taylor wrote: > On 7/1/23 3:09 AM, Paul Jensen wrote: > > > On Wed, Jun 28, 2023 at 5:33 AM Yoav Weiss wrote: > >> >> >> On Tue, Jun 27, 2023 at 9:54 PM Paul Jensen >> wrote: >> >>> Yoav, >>> >>> Protected Audiences has been fortunate to have a ton of

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

On 7/1/23 3:09 AM, Paul Jensen wrote: On Wed, Jun 28, 2023 at 5:33 AM Yoav Weiss wrote: On Tue, Jun 27, 2023 at 9:54 PM Paul Jensen wrote: Yoav, Protected Audiences has been fortunate to have a ton of design contributions and feedback, but consequently

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

On Wed, Jun 28, 2023 at 5:33 AM Yoav Weiss wrote: > > > On Tue, Jun 27, 2023 at 9:54 PM Paul Jensen > wrote: > >> Yoav, >> >> Protected Audiences has been fortunate to have a ton of design >> contributions and feedback, but consequently has a lot of issues filed. We >> try to respond to all

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

On Tue, Jun 27, 2023 at 9:54 PM Paul Jensen wrote: > Yoav, > > Protected Audiences has been fortunate to have a ton of design > contributions and feedback, but consequently has a lot of issues filed. We > try to respond to all issues, as you can see by the discussion comments on > nearly all

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

Yoav, Protected Audiences has been fortunate to have a ton of design contributions and feedback, but consequently has a lot of issues filed. We try to respond to all issues, as you can see by the discussion comments on nearly all issues. I went through and triaged all the issues recently. I

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

Glancing at the open issues, I see 291 of them .. Would it be possible to go over the issues and label them so that it's clearer which are about future enhancements, which are editorial and which may have an impact on the processing model

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

As the spec mentor for this feature I'll offer a spec maturity summary

[blink-dev] Intent to Ship (I2S): Protected Audience

*Contact emails* pauljen...@chromium.org, kle...@google.com, ajvelasq...@google.com Explainer https://github.com/WICG/turtledove/blob/master/FLEDGE.m d Specification https://wicg.github.io/turtledove Summary The Protected Audience