You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rationale behind this rule is to provide an option that safely disables "Protected Audience API". Disabling it may be required by privacy filter lists.
Protected Audience API is supposed to be a "private" alternative to third-party cookies tracking for showing targeted ads. While this is indeed a more private alternative, the downside is that it transforms the browser itself into an ad auction tool.
I honestly cannot see how this design is more private.
What should be implemented
This scriptlet is similar to #214 and the purpose is to suppress "Protected Audience API" functions.
The scriptlet should work in a similar fashion to no-topics: check if the specified properties exist and replace them with noop stubs.
The full list of functions can be found here: https://wicg.github.io/turtledove/
Please check the functions signature and replace it with a stub that has the same signature.
Here's a list of functions that we need to override:
…criptlets#395
- added `Suppressing Private State Token API` Closes#175725
- changed `Suppressing both Google's Topics API and Topics API using Permissions policy` (related to `TODO: remove $document modifier after versions with Corelibs 1.14.38+ will be released`)
* - added `Suppressing Google's "Protected" Audience API` AdguardTeam/Scriptlets#395
- added `Suppressing Private State Token API` Closes#175725
- changed `Suppressing both Google's Topics API and Topics API using Permissions policy` (related to `TODO: remove $document modifier after versions with Corelibs 1.14.38+ will be released`)
Why do we need this?
The rationale behind this rule is to provide an option that safely disables "Protected Audience API". Disabling it may be required by privacy filter lists.
Protected Audience API is supposed to be a "private" alternative to third-party cookies tracking for showing targeted ads. While this is indeed a more private alternative, the downside is that it transforms the browser itself into an ad auction tool.
Moreover, the browser will in the background (without user knowing about it) contact configured URLs to update the "interest group" or reload the bidding logic: https://developers.google.com/privacy-sandbox/relevance/protected-audience-api/interest-groups
I honestly cannot see how this design is more private.
What should be implemented
This scriptlet is similar to #214 and the purpose is to suppress "Protected Audience API" functions.
The scriptlet should work in a similar fashion to
no-topics
: check if the specified properties exist and replace them with noop stubs.The full list of functions can be found here: https://wicg.github.io/turtledove/
Please check the functions signature and replace it with a stub that has the same signature.
Here's a list of functions that we need to override:
Navigator.prototype.joinAdInterestGroup
Navigator.prototype.runAdAuction
Navigator.prototype.leaveAdInterestGroup
Navigator.prototype.clearOriginJoinedAdInterestGroups
Navigator.prototype.createAuctionNonce
Navigator.prototype.updateAdInterestGroups
The text was updated successfully, but these errors were encountered: