Blocked on third LGTM for I2S

[Paul Jensen]

As per this policy, I'm reaching out to ask for a third LGTM or feedback on my I2S which has 2 LGTMs (from Yoav and Mike T.) and no open or unaddressed feedback and has been blocked for five days:

https://groups.google.com/a/chromium.org/g/blink-dev/c/3RUQk0GCC9Q

Thank you,
Paul

[Daniel Bratell]

We took a look at "Intent to Ship: Protected Audience: Downsampled forDebugOnly & Increase number of component ads"  today (would have happened anyway, but we really took a look at it today), and I just want to give a quick summary of my position here:

The intent is unfortunately for two things. The debug thing seems very much under control and I could lgtm that part today, but the the other part I don't fully grasp the consequences of. Even if the privacy difference is "negligible", it exists. The chromestatus privacy review unfortunately only mentions the first half of the intent, not the part which is admittedly a negative change, negligible or not, which also makes me wonder if they reviewed both parts.

If someone could flesh out the privacy analysis information in the intent thread, targetting people that are much less involved in the work than you are, that might help. Or maybe one of the other API owners that know more can jump in, or maybe someone from the Google privacy team can add their "both parts are fine" on the thread?

/Daniel

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CABQTWr%3Dh-bN1RgsZKmCe2ECJWarjX%3DWWERqF59pU31iWKeX3vg%40mail.gmail.com.