[blink-dev] Fwd: Intent to Extend Experiment: Protected Audience Bidding & Auction Services

(Now *To* blink-dev instead of just CC) 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:

[blink-dev] Intent to Extend Experiment: Protected Audience Bidding & Auction Services

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

[blink-dev] Re: PSA: Protected Audience k-Anonymity Enforcement

FYI: We are currently in the process of ramping k-anonymity enforcement back up to 1% of eligible traffic on Stable channel. As before, eligible traffic is pre-stable and stable channels, excluding Mode A and Mode B traffic. Best, --Benjamin "Russ" Hamilton On Mon, Apr 8, 2024 at 1:20 PM Russ

Re: [blink-dev] Intent to Extend Experiment: Protected Audience Bidding & Auction Services

>> bit.ly/blink-signals requests >> Outreach for feedback from the spec community >> WPT tests >> >> I recognize some of this is touched on in your email - but having it >> explicitly in one spot would be helpful, thanks. >> On 4/4/24 12:19 PM, 'Rus

Re: [blink-dev] Intent to Extend Experiment: Protected Audience Bidding & Auction Services

one spot would be helpful, thanks. > On 4/4/24 12:19 PM, 'Russ Hamilton' via blink-dev wrote: > > Contact emails > > pauljen...@chromium.org, behamil...@google.com > > Explainer > > Chrome: > https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_a

[blink-dev] Re: PSA: Protected Audience k-Anonymity Enforcement

FYI: We are planning to ramp k-anonymity enforcement back up to 50% of eligible traffic on Beta channel later today. Best, --Benjamin "Russ" Hamilton On Wed, Apr 3, 2024 at 1:25 PM Russ Hamilton wrote: > Recently, we became aware that Chrome was mistakenly applying k-anonymity > enforcement on

[blink-dev] Intent to Extend Experiment: Protected Audience Bidding & Auction Services

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

[blink-dev] Re: PSA: Protected Audience k-Anonymity Enforcement

Recently, we became aware that Chrome was mistakenly applying k-anonymity enforcement on reporting to a portion of Mode A and Mode B testing traffic . This did not affect ad selection and therefore should

[blink-dev] Re: Intent to Experiment: Cookie Deprecation Labeling

FYI, based on feedback from testers (https://github.com/WICG/turtledove/issues/946) we are going to send the Cookie-Deprecation label headers during the trusted bidding and trusted scoring signals fetches for Protected Audience auctions beginning in M122. Note that if the user is not part of

Re: [blink-dev] PSA: Protected Audience k-Anonymity Enforcement

Mike Taylor wrote: > Hi Russ, > > Can you say more about the compatibility implications for such a change? > AFAIU, things shouldn't "break" for users or throw errors behind the > scenes, correct? > > thanks, > Mike > On 1/26/24 12:59 AM, 'Russ Hamilton' via

[blink-dev] PSA: Protected Audience k-Anonymity Enforcement

We plan to start enabling the k-anonymity enforcement feature for the Protected Audience API (Intent to Ship