[blink-dev] Intent to Ship: Protected Audience: Downsampled forDebugOnly & Increase number of component ads

Contact emails pauljen...@chromium.org Explainer Downsampled forDebugOnly: https://github.com/WICG/turtledove/pull/1020 Increase number of component ads: https://github.com/WICG/turtledove/pull/1003 Specification Downsampled forDebugOnly: https://github.com/WICG/turtledove/pull/1023

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

u want to batch it together that sounds fine to me. Can you: >>>> >>>> * Update the chromestatus entry >>>> <https://chromestatus.com/feature/5021508157571072> accordingly >>>> (including shipping milestones, updated description, and >>

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

those two PRs for the spec and explainer > > Then the API owners can review again and re-issue 3 new LGTMs if it looks > good. > > On Wed, Nov 8, 2023 at 11:47 AM 'Orr Bernstein' via blink-dev < > blin...@chromium.org> wrote: > >> Hi Chris, >> >> Thanks

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

ing to batch these additional changes together with that, and > consider these new changes thematically related? If not, I think it would > be more clear to make a new I2S and chromestatus entry. > > On Wed, Nov 8, 2023 at 9:58 AM 'Orr Bernstein' via blink-dev < > blin...@chromium.org

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

t 11:00:07 PM UTC+2 Mike Taylor wrote: >>>> >>>>> LGTM1 % landing https://github.com/WICG/turtledove/pull/796. Please >>>>> follow up with the WPTs as well. >>>>> On 9/27/23 11:56 AM, Chris Harrelson wrote: >>>>> >>>&g

Re: [blink-dev] Intent to Ship: Protected Audience clearOriginJoinedAdInterestGroups() & interest group limit changes & kAnonStatus

Thank you, all! On Wed, Nov 8, 2023 at 11:48 AM Chris Harrelson wrote: > LGTM3 > > On Wed, Nov 8, 2023 at 8:35 AM Mike Taylor wrote: > >> LGTM2 >> On 11/8/23 11:33 AM, Yoav Weiss wrote: >> >> LGTM1 >> >> On Wednesday, November 1, 2023 at 8:11:02 PM UTC+1 or...@google.com >> wrote: >> >>> Sorry

Re: [blink-dev] Intent to Ship: Protected Audience clearOriginJoinedAdInterestGroups() & interest group limit changes & kAnonStatus

Sorry for the delay in response. All of the PRs have since landed. Regarding your question on the interest group limit changes, these limits are intended to be guardrails against exceptional behavior, and not meant to be reached under normal conditions. In the best practices we previously

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

>> >>>> Please fill out the other chromestatus review categories (privacy, >>>> security, etc); we'll re-review once those are done. >>>> >>>> On Wed, Sep 20, 2023 at 2:42 PM 'Orr Bernstein' via blink-dev < >>>> blin...@chromium.org> wrote

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

gt;>> >>> Please fill out the other chromestatus review categories (privacy, >>> security, etc); we'll re-review once those are done. >>> >>> On Wed, Sep 20, 2023 at 2:42 PM 'Orr Bernstein' via blink-dev < >>> blink-dev@chromium.org> wrote: >&

[blink-dev] Intent to Ship: Protected Audiences Negative Targeting

Contact emails o...@google.com, pauljen...@chromium.org Explainer https://github.com/WICG/turtledove/pull/780 Specification https://github.com/WICG/turtledove/pull/796 Summary In online ad auctions for ad space, it’s sometimes useful to prevent showing an ad to certain audiences, a concept