Contact emailsale...@chromium.org
Explainer
https://github.com/WICG/turtledove/blob/main/FLEDGE_extended_PA_reporting.md#temporary-debugging-mechanism
Specification
https://github.com/patcg-individual-drafts/private-aggregation-api/pull/118
Summary
Adds support for Private Aggregation’s debug m
Alex and Yoav,
This particular addition is exposed only as an optional parameter on the
existing `AuctionAdConfig` dictionary passed to `navigator.runAdAuction()`.
So, I'm not aware of any web visibility from removing the new
`auctionReportBuyerDebugModeConfig` field (if it was already having no
e
On Thu, Mar 7, 2024 at 5:03 PM Alex Turner wrote:
> Alex and Yoav,
>
> This particular addition is exposed only as an optional parameter on the
> existing `AuctionAdConfig` dictionary passed to `navigator.runAdAuction()`.
> So, I'm not aware of any web visibility from removing the new
> `auctionR
LGTM3
I agree with Alex that we have a bad track record of "temporary" APIs on
the web, but I'm comfortable with this given the particulars. A feature
which is only a dictionary member is detectable (through a getter) but you
have to do extra work and I don't recall ever seeing a problem from
remo
LGTM1
On Thu, Feb 29, 2024 at 7:29 PM Alex Turner wrote:
> Contact emailsale...@chromium.org
>
> Explainer
> https://github.com/WICG/turtledove/blob/main/FLEDGE_extended_PA_reporting.md#temporary-debugging-mechanism
>
> Specification
> https://github.com/patcg-individual-drafts/private-aggregati
LGTM2
On 3/6/24 5:39 AM, Yoav Weiss (@Shopify) wrote:
LGTM1
On Thu, Feb 29, 2024 at 7:29 PM Alex Turner wrote:
Contact emails
ale...@chromium.org
Explainer
https://github.com/WICG/turtledove/blob/main/FLEDGE_extended_PA_reporting.md#temporary-debugging-me
Hey all,
This may be overfitting against my personal priors, but I'm *intensely
*skeptical
of any web platform API addition that claims to be "temporary". If we want
a temporary mechanism, we can use OTs and set a date-certain for removal
and prevent over-use that would back us into a corner.
Hey Alex,
Totally understand the concern given how difficult removing web APIs
typically is. However, I think for this case removal should be much simpler
as the functionality (and debug mode more generally) is already tied to
third-party cookie eligibility*. In other words, after third-party cook
Removal being guaranteed to be backwards compatible depends, at a minimum,
on nullability. As this API would, instead, be globally exposed (but would
not "work" when 3p cookie ineligible), addition and removal present the
usual crop of addition and deprecation issues.
3p cookie turndown is now int
Alex T - can you expand on the other debug modes that are already shipped?
Are they also tied to 3P cookie eligibility?
If so, I agree that having all these mechanisms activated together and stop
working together makes sense.
On Wed, Mar 6, 2024 at 11:04 PM Alex Russell
wrote:
> Removal being g
10 matches
Mail list logo
