[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] 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] 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:

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: >>&g

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

, 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 here, you're trying &

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

ere? > > 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: > > > > On

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

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

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

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:

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 Ad slot size in real-time bidding signals fetch and update more interest group fields

oncern 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 > > > > On Fri, J

[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

[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

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

lson 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...@g

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

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

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

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 migrating their users sh

[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

[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

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

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

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

[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] Re: Intent to Experiment: First "Locally-Executed Decision over Groups" Experiment (FLEDGE)

s of 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

[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

[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