Could Privacy Badger integrate some features of Privacy Possum?

[0x391F]

Privacy Possum's (PP) on Github
https://github.com/cowlicks/privacypossum

PP seems doen't maintiance anymore, and it sometimes break some webpages.

Some important features of PP:

• Inject random data to spoil the first party fingerprint
• Etag blocking
• Referer headers blocking

[ghostwords]

Hello and thanks for getting in touch!

• Regarding fingerprinting defenses, please see the discussion in Current anti-fingerprinting status? #2567. The gist is that this is something best left to the browser.
• For ETags, please subscribe to Detect etag supercookies #2136 for updates.
• Browsers at this point default to some version of the strict-origin-when-cross-origin referrer policy, which means cross-origin requests receive origins only (instead of full URLs). Privacy Badger also enforces origin-only referrers for all cookieblocked requests (Use origin-only referrers with cookieblocked requests #2505). I'm not sure blocking referrer headers entirely makes sense for us, as it tends to break sites (some examples, many more cases from Brave, Strip referer to strict-origin-when-cross-origin in all cases brave/brave-browser#13464). We could though look into enforcing origin-only referrers for all third-party requests (and further trimming cookieblocked request referrers to eTLD+1), to emulate Safari's behavior in all browsers.

Let me know if you have any questions.