Don Marti

Under key needs of publishers, it could be a good idea to include: * Block [data leakage](https://digitalcontentnext.org/blog/2016/01/06/is-your-data-leaking/). The system must not make the fact that the user has visited one...

@ClearlyClaire Yes, I have the same understanding. The benefit of #19971 will be to keep the opt out working if/when Google Chrome stops supporting the legacy header. Thank you, this...

@leo60228 This could apply to any instance that uses any third-party script. Unless you use Subresource Integrity and do a code review on all third-party scripts, any third party script...

@leo60228 That is a good idea, you should probably make a separate issue for it though.

Another possible use case for this proposal is QA. A variety of things could break in production, some of which could be hard to detect in advance. * Site has...

Does DFP in non-personalized mode meet the criteria for yellow listing? https://github.com/EFForg/privacybadger/blob/master/doc/yellowlist-criteria.md One item is "Is the domain's privacy policy clear that it does not perform non-consensual tracking?" I can...

@AramZS So ideally you would want to be able to do something like this... * if the page has Google Tag Manager, inject JS to put all the Google scripts...

@AramZS There's an item in the FAQ: **I am an online advertising / tracking company. How do I stop Privacy Badger from blocking me?** Another question is: "I am using...

@snarfed Thank you. It might be possible to avoid the registry by saying this only applies to options available to users, and does not apply to HTTP headers that a...

Update: FEP at https://codeberg.org/fediverse/fep/src/branch/main/fep/5e53/fep-5e53.md