[blink-dev] Intent to Ship: Protected Audience directFromSellerSignals via HTTP response headers

Contact emails *pauljen...@chromium.org *Explainer *https://github.com/WICG/turtledove/pull/69 5*Specification *https://github.com/WICG/turtledove/pull/771 https://github.com/WICG/turtledove/pull/774

[blink-dev] Intent to 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] Intent to Ship: Protected Audience clearOriginJoinedAdInterestGroups() & interest group limit changes & kAnonStatus

Contact emails pauljen...@chromium.org Explainer clearOriginJoinedAdInterestGroups(): https://github.com/WICG/turtledove/pull/829 interest group limit changes: https://github.com/WICG/turtledove/pull/839 kAnonStatus: https://github.com/WICG/turtledove/pull/714 Specification clearOriginJoin

[blink-dev] Intent to Ship: Protected Audience Ad slot size in real-time bidding signals fetch and update more interest group fields

Contact emails pauljen...@chromium.org Explainer Ad slot size in real-time bidding signals fetch: https://github.com/WICG/turtledove/pull/928 Update more interest group fields: Already covered by explainer

Re: [blink-dev] Intent to Ship: Protected Audience Ad slot size in real-time bidding signals fetch and update more interest group fields

ern is that this spec > PR <https://github.com/WICG/turtledove/pull/954> hasn't been reviewed > yet, and we generally prefer for all tests to land before approval. Would > it be reasonable to get those done before we approve this? > > Thanks, >Rick > > > >

[blink-dev] Re: Intent to Ship: WebAssembly Relaxed SIMD

>> For FMA, on x86, everything from Haswell (2013) onwards, and Piledriver (2012) onwards on AMD support native FMA operations. On ARM64, Neon support implies FMA would be natively supported as well (Neon is the baseline on ARM64 for being able to generate any vector instructions). On Arm32, t

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

Contact emailspauljen...@chromium.org, kle...@google.com Explainer Browser API: https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md Bidding & Auction Services: https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md Specificatio

[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 API

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

that document the current >> implementation, there will probably be minor web-visible changes after >> shipping in M115. However, most of these changes are unlikely to break web >> content, and if anything bigger comes up, the Privacy Sandbox's general >> tools for

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 iss

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, >>&

[blink-dev] Intent to Ship: Protected Audience features: recency, rounding bids & scores

Contact emails pauljen...@chromium.org Explainer https://github.com/WICG/turtledove/pull/639/files?short_path=d65ba97#diff-d65ba9778fe3af46de3edfce2266b5b035192f8869280ec07179963b81f4e624 https://github.com/WICG/turtledove/pull/486/files?short_path=d65ba97#diff-d65ba9778fe3af46de3edfce2266b5b03

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

On Wed, Feb 28, 2024 at 12:24 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Thu, Feb 22, 2024 at 6:07 PM 'Orr Bernstein' via blink-dev < > blink-dev@chromium.org> wrote: > >> Contact emails >> >> pauljen...@chromium.org >> >> >> Explainer >> >> Downsampled forDebugOnly: https:

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

On Wed, Mar 6, 2024 at 12:07 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Mon, Mar 4, 2024 at 7:00 PM Paul Jensen > wrote: > >> >> >> On Wed, Feb 28, 2024 at 12:24 PM Yoav Weiss (@Shopify) < >> yoavwe...@chromium.org> wr

[blink-dev] Intent to Ship: Protected Audience: Split up large trusted signals fetches & deprectedReplaceInURN via auction config

Contact emails pauljen...@chromium.org Explainer Split up large trusted signals fetches: https://github.com/WICG/turtledove/pull/1070 deprectedReplaceInURN via auction config: https://github.com/WICG/turtledove/pull/1069 Specification Split up large trusted signals fetches: https://github.c

Re: [blink-dev] Intent to Ship: Protected Audience: Split up large trusted signals fetches & deprectedReplaceInURN via auction config

happen here? > > Either way, I worry that this could become a source of random problems > that would be hard to understand or debug. Is there any third or fourth > option to consider? > > /Daniel > On 2024-03-25 17:44, 'Paul Jensen' via blink-dev wrote: > > > >

Re: [blink-dev] Intent to Ship: Protected Audience: Split up large trusted signals fetches & deprectedReplaceInURN via auction config

> >> LGTM3 >> >> /Daniel >> On 2024-04-08 17:37, Yoav Weiss (@Shopify) wrote: >> >> LGTM2 >> >> On Mon, Apr 8, 2024 at 5:36 PM Mike Taylor >> wrote: >> >>> LGTM1 >>> On 4/3/24 11:05 AM, Daniel Bratell wrote: >&

[blink-dev] Intent to Ship: Protected Audience: reporting timeouts & multiple-bids

Contact emails pauljen...@chromium.org Explainer Protected Audience reporting timeouts: https://github.com/WICG/turtledove/pull/1101 Protected Audience multiple-bids: https://github.com/WICG/turtledove/pull/1048 Specification Protected Audience reporting timeouts: https://github.com/WICG/tu

[blink-dev] Re: Intent to Ship: Protected Audience: reporting timeouts & multiple-bids

On Wed, May 15, 2024 at 8:36 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Monday, May 6, 2024 at 10:03:16 PM UTC+2 Paul Jensen wrote: > > Contact emails > > pauljen...@chromium.org > > > Explainer > > Protected Audience r

[blink-dev] Re: Intent to Ship: Protected Audience: reporting timeouts & multiple-bids

Actually CC Erik this time. On Fri, May 17, 2024 at 8:40 AM Paul Jensen wrote: > > > On Wed, May 15, 2024 at 8:36 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Monday, May 6, 2024 at 10:03:16 PM UTC+2 Paul Jensen wr

[blink-dev] Intent to Ship: Protected Audience: Allow trusted bidding signals to trigger interest group updates

Contact emails pauljen...@chromium.org Explainer https://github.com/WICG/turtledove/pull/1095 Specification https://github.com/WICG/turtledove/pull/1124 Summary The Protected Audience API allows bidders to store information, called an interest group, from a single site in the browser that

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

Mike, It looks like we did continue the OT during M122-124 before sending the first I2EE, despite initially only asking for approval for M119-121. I wonder if someone went off of the current OT policy of "An initial origin trial or experiment for a feature may only run for 6 milestones"

[blink-dev] Intent to Ship: Protected Audience: cross-origin trusted signals fetches

Contact emails pauljen...@chromium.org Explainer https://github.com/WICG/turtledove/pull/1156 Specification https://github.com/WICG/turtledove/pull/1197 Side note: there are two related clarification spec PRs (1 , 2

Re: [blink-dev] Intent to Ship: Protected Audience: cross-origin trusted signals fetches

s, and the first one of the two has landed. On Fri, Jul 19, 2024 at 4:40 PM Paul Jensen wrote: Summary This feature allows the Protected Audience (PA) API to fetch real-time bidding and scoring signals from origins other than the origin of the buyer and seller's scripts. This is don

[blink-dev] Intent to Ship: Protected Audience: Real Time Monitoring API

Contact emails pauljen...@chromium.org Explainer https://github.com/WICG/turtledove/blob/main/PA_real_time_monitoring.md Specification https://github.com/WICG/turtledove/pull/1212 Summary The goal of real-time monitoring is to get Protected Audience API auction monitoring data to the buye

[blink-dev] Re: Intent to Ship: Protected Audience: Real Time Monitoring API

We also extended our feature detection API to facilitate detecting this feature: Explainer: https://github.com/WICG/turtledove/pull/1238 Spec: https://github.com/WICG/turtledove/pull/1245 On Wednesday, July 31, 2024 at 12:51:08 PM UTC-4 Paul Jensen wrote: > Contact emails > >

Re: [blink-dev] Intent to Ship: Protected Audience: cross-origin trusted signals fetches

On Wed, Aug 7, 2024 at 11:25 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > On Wednesday, July 31, 2024 at 6:38:43 PM UTC+2 Paul Jensen wrote: > > Previous to this proposal, the trusted signals were required to come from > the same origin as the bidding or s

Re: [blink-dev] Re: Intent to Ship: Protected Audience: Real Time Monitoring API

ps://github.com/WICG/turtledove/pull/1212#issuecomment-2273987026>), > should we wait for those to resolve? > > On Thu, Aug 8, 2024 at 11:32 AM Paul Jensen > wrote: > >> We also extended our feature detection API to facilitate detecting this >> feature: >> Expl

[blink-dev] Re: Intent to Experiment: First "Locally-Executed Decision over Groups" Experiment (FLEDGE)

on 4/26 ><https://chromiumdash.appspot.com/schedule>? > > Thank you, > > Geoff > On Thursday, March 31, 2022 at 5:38:49 AM UTC-6 Paul Jensen wrote: > >> On Wed, Mar 30, 2022 at 5:53 AM Yoav Weiss wrote: >> > On Friday, March 25, 2022 at 11:46:45 PM

Re: [blink-dev] Intent to Ship: Default SVG cursor size set from OS settings

Is the SVG cursor size discernible to the site? On Thursday, May 26, 2022 at 9:18:09 PM UTC-4 Chris Harrelson wrote: > Hi Sahir, > > On Thu, May 26, 2022 at 1:44 PM 'Sahir Vellani' via blink-dev < > blink-dev@chromium.org> wrote: > >> Platform cursor size used as default for custom SVG cursors if

Re: [blink-dev] Re: FYI Privacy Sandbox Ads APIs origin trial

Hi folks. In regards to the FLEDGE bug and subsequent ramp down of FLEDGE for Chrome Stable, I wanted to bring your attention to a post from the FLEDGE API Announce list yesterday that impacts experim

[blink-dev] Intent to Experiment: First "Locally-Executed Decision over Groups" Experiment (FLEDGE)

Contact emails pauljen...@chromium.org , kle...@google.com Developers interested in the FLEDGE API can also join the FLEDGE API announcements group for updates and announcemen

[blink-dev] Re: Intent to Experiment: First "Locally-Executed Decision over Groups" Experiment (FLEDGE)

On Wed, Mar 30, 2022 at 5:53 AM Yoav Weiss wrote: > > > On Friday, March 25, 2022 at 11:46:45 PM UTC+1 Paul Jensen wrote: > >> Contact emails >> >> pauljen...@chromium.org <https://groups.google.com/>, kle...@google.com >> <https://groups.google.co

Re: [blink-dev] Re: Intent to Experiment: First "Locally-Executed Decision over Groups" Experiment (FLEDGE)

f its rollout? > This debugging functionality is included in this experiment. > On Thursday, March 31, 2022 at 6:47:46 AM UTC-7 yoav...@chromium.org > wrote: > >> LGTM to experiment till M104, inclusive >> >> On Thu, Mar 31, 2022 at 1:38 PM Paul Jensen >> wrot

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

Yoav, our IETF service spec repository is already public and we verified anyone can file issues there. We also verified with more experienced standardization folks that its IPR settings look right. On Wed, Oct 16, 2024 at

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

uecomment-2432121278> and here <https://github.com/mozilla/standards-positions/issues/770#issuecomment-2432124085> . On Wed, Oct 23, 2024 at 12:29 PM Paul Jensen wrote: > Erik, > > Edge recently started an Origin Trial for the Ad Selection API > <https://blogs.windows.com/msed

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

ction-services/draft-ietf-bidding-and-auction-services.html> ? 3. We recently posted the location and format of the coordinator keys that Chrome fetches <https://github.com/WICG/turtledove/pull/1309/files>. Does the Ad Selection API use a similar mechanism? On Fri, Oct 18,

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

S and GCP, but I believe > that detail is out of scope here. > > Thanks, > > Erik > > > > *From:* Yoav Weiss (@Shopify) > *Sent:* Wednesday, October 30, 2024 3:10 AM > *To:* blink-dev > *Cc:* Mike Taylor ; blink-dev < > blink-dev@chromium.org>; Manny

[blink-dev] Intent to Deprecate and Remove: Protected Audience Subresource bundle directFromSellerSignals

Contact emails carai...@chromium.org pauljen...@chromium.org Summary The Protected Audience API provides 2 mechanisms that allow signals to be passed into auctions in such a way that ensures the authenticity and integrity of the signals: the original version

[blink-dev] PSA: Enabling 5 Protected Audience and Fenced Frame features in Mode A/B

Five Protected Audience (PA) and Fenced Frames (FF) features were shipped earlier this year but not enabled in the Chrome-facilitated testing Modes A and B to prevent disrupting experiments and

Re: [blink-dev] Intent to Ship: Protected Audience (B&A) - Selectable Reporting IDs

cked for k-anonymity and verified to be present in the interest group. > Also, more meta question: are there scenarios where you would ship a > feature to PA but not ship support for PA/B&A? > I can't think of any. I think we always design PA features so they'll be feasible o

[blink-dev] Intent to Ship: Protected Audience (B&A) - Private Aggregation & downsampling forDebuggingOnly reporting

Contact emails pauljen...@chromium.org qingxi...@google.com Explainer For original Protected Audience Private Aggregation reporting support: https://github.com/WICG/turtledove/pull/386 For original Protected Audience downsampling forDebuggingOnly reporting: https://github.com/WICG/turtledove/

[blink-dev] Intent to Ship: Protected Audience (B&A) - Selectable Reporting IDs

Contact emails pauljen...@chromium.org Explainer For original Protected Audience Selectable Reporting IDs support: https://github.com/WICG/turtledove/pull/1237 Specification Web spec: https://github.com/WICG/turtledove/pull/1348 Protocol spec: https://github.com/privacysandbox/draft-ietf-bi

[blink-dev] Intent to Ship: Protected Audience: Trusted Key-Value Server Support

Contact emails pauljen...@chromium.org Explainer https://github.com/WICG/turtledove/pull/1342 https://github.com/WICG/turtledove/pull/1343 Specification The web platform portion of the specification: https://github.com/WICG/turtledove/pull/1340 The interface to the Trusted Key-Value Server e

Re: [blink-dev] Re: Intent to Ship: Protected Audience: Trusted Key-Value Server Support

elson wrote: > > > On Wed, Jan 15, 2025 at 10:29 AM Paul Jensen > wrote: > >> The main relevant section of the Protected Audience explainer is 3.1.2 >> Trusted Signals Server in TEE >> <https://github.com/WICG/turtledove/blob/main/FLEDGE.md#312-trusted-sig

Re: [blink-dev] Intent to Ship: Protected Audience (B&A) - Private Aggregation & downsampling forDebuggingOnly reporting

The Private Aggregation ones landed here <https://chromium-review.googlesource.com/c/chromium/src/+/6164350>. The downsampled forDebugginOnly ones are in progress. On Wed, Dec 18, 2024 at 4:12 PM Mike Taylor wrote: > Can you let us know when you have landed WPTs? > On 12/17/24 3

[blink-dev] Intent to Ship: Protected Audience: Private Aggregation per-participant usage metrics

Contact emails pauljen...@chromium.org Explainer https://github.com/WICG/turtledove/pull/1272 Specification https://github.com/WICG/turtledove/pull/1321 https://github.com/WICG/turtledove/pull/1328 https://github.com/WICG/turtledove/pull/1341 https://github.com/WICG/turtledove/pull/1349 htt

[blink-dev] Re: Intent to Ship: Protected Audience: Trusted Key-Value Server Support

Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Wednesday, January 8, 2025 at 5:59:00 PM UTC+1 Paul Jensen wrote: > > Contact emails > > pauljen...@chromium.org > > Explainer > > https://github.com/WICG/turtledove/pull/1342 > > https://github.co

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

Harrelson wrote: > > Please fill out and start the reviews for Privacy, Security and > Debuggability in your chromestatus entry, thanks. > > On Thu, Oct 12, 2023 at 3:40 PM Paul Jensen > wrote: > >> Contact emails >> >> pauljen...@chromium.org, behamil

Re: [blink-dev] Intent to Ship: Protected Audience Ad slot size in real-time bidding signals fetch and update more interest group fields

On Wed, Jan 24, 2024 at 8:29 PM Domenic Denicola wrote: > > > On Sat, Jan 6, 2024 at 3:05 AM Paul Jensen > wrote: > >> Contact emails >> >> pauljen...@chromium.org >> >> >> Explainer >> >> Ad slot size in real-time biddin

Re: [blink-dev] Intent to Ship: Protected Audience: Split up large trusted signals fetches & deprectedReplaceInURN via auction config

On Wed, Mar 20, 2024 at 2:02 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Thu, Mar 14, 2024 at 8:48 PM Paul Jensen > wrote: > >> Contact emails >> >> pauljen...@chromium.org >> >> >> Explainer >> >&g

Re: [blink-dev] Intent to Ship: Protected Audience: Split up large trusted signals fetches & deprectedReplaceInURN via auction config

n Wed, Mar 27, 2024 at 1:57 PM Mike Taylor wrote: > On 3/25/24 12:44 PM, 'Paul Jensen' via blink-dev wrote: > > On Wed, Mar 20, 2024 at 2:02 PM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > > If I understand correctly what y'all are trying to do h

Re: [blink-dev] Intent to Deprecate and Remove: Protected Audience Subresource bundle directFromSellerSignals

t;>> non-Finch justification, and Estimated milestones. >>>> >>>> Some of these are probably not too serious given the low volume of >>>> usage, e.g. I suspect no special debuggability support is required. But >>>> it'd be helpful to include them all. >