Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add clearOriginJoinedAdInterestGroups() #4

Closed
wants to merge 25 commits into from

Conversation

MattMenke2
Copy link
Owner

@MattMenke2 MattMenke2 commented Sep 25, 2023

This is a proposed API to make managing interest groups on a per-joining-top-level-origin basis easier. See issue WICG#475 for the motivating proposal.

MattMenke2 and others added 25 commits September 25, 2023 13:15
This is a proposed API to make managing interest groups on a per-joining-top-level-origin basis easier.
Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>
Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>
email updated for Magnite
* Add auction server request flags

* Address comments

* Update FLEDGE.md

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>

* Add auctionServerRequestFlags to example

* fix typo

---------

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>
Add bit of clarity on destinations being to be both buyer and seller rather than one or other.
Joining an interest group with a duration of 0 effectively leaves it, so spell that out in the spec.  An alternative option would be to ignore the .well-known permissions if only join is allowed, or if join is allowed but leave is explicitly disallowed.
In the most recent version of the additional bids/negative targeting
design, additional bids are transported via HTTP response headers, so
that sellers don't have a risk for which they'd need a differently named
reporting function to acknowledge that risk. The text in the explainer
correctly noted the risk to buyers, and the differently named reporting
function for buyers, `reportAdditionalBidWin`, remains.
* Make negative interest groups non-updatable

In a previous version of the negative targeting design, negative interest groups were updatable so that the additional bid key could be rotated more frequently than every 30 days. We've updated this design so that negative interest groups are non-updatable, and the additional bid key should be rotated exactly every 30 days.

* Make negative interest groups non-updatable

In a previous version of the negative targeting design, negative interest groups were updatable so that the additional bid key could be rotated more frequently than every 30 days. We've updated this design so that negative interest groups are non-updatable, and the additional bid key should be rotated exactly every 30 days.
…CG#842)

When an additional bid specifies two or more negative interest groups, it must also identify a single joining origin for all of those negative interest groups. Any negative targeting group joined for a different origin than the one specified is treated as if it's not present. This change emphasizes this policy of "failing open", as the explainer already does for signature verification errors.
…vailable. (WICG#622)

* Added info about when the ad component support is available.

* Mention that all combination of urn-iframe and fenced frame works.

* Update Fenced_Frames_Ads_Reporting.md

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>

* Update Fenced_Frames_Ads_Reporting.md

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>

---------

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>
* Update FLEDGE_k_anonymity_server.md

I believe this paragraph of the K Anon Server doc was out of date, not updated for the decision to not do k-anon checks on the dailyUpdateUrl.

* Update FLEDGE_k_anonymity_server.md

Add snippet about k-anon application at buyer reporting time.
* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs

* Update spec.bs
* Handle directFromSellerSignalsHeaderAdSlot

* Handles header-based directFromSellerSignals.

Resolves auction config's directFromSellerSignalsHeaderAdSlot promise.
Passes directFromSellerSignals to worklets (generateBid(), scoreAd(),
reportWin(), reportResult()).

* Address comments, and pass signal to top level auction.

* Small change.

* Return failure if ad slot promise resolves failure.

* Define IDLs for directFromSellerSignals and convert to JS.

* Add or-undefined to direct seller signals parameter.

* Cleanup

* Address comments.

* Some fix.

* Address comments

* Address Dom's comments.

* Address Caleb's comments.

* Address Caleb's comments

* Parse signals json before passed to worklets.

* Random commit to regenerate preview.

* Address Dom's comments.

* Address Dom's comments.

* address nit

* remove section redundant with 771

* fix name of captured headers

* add link

* fix link syntax

---------

Co-authored-by: Qingxin Wu <qingxinwu@google.com>
Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>
* Update FLEDGE.md

Add description of a new field "kAnonStatus" in reportWin() to provide users of K-anon an easy way to understand the impact of K-anon without hard enforcement that removes ads.

* Update kAnonStatus description.

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>

* Update passedAndEnforced description.

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>

* Update passedNotEnforced description.

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>

* Update belowThreshold description.

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>

* Update notCalculated description.

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>

---------

Co-authored-by: Paul Jensen <JensenPaul@users.noreply.github.com>
@MattMenke2 MattMenke2 closed this Nov 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet