Re:Open research, stronger privacy: Making Firefox users har...
by skaul on Wednesday November 11, 2026 @12:56PM
(#50456346)
If by "tainting" the data you mean subtly changing it in a way that preserves functionality while making it harder to use for fingerprinting, then this is what we do at Brave browser for many of our anti-fingerprinting protections: https://brave.com/glossary/fingerprinting/#how-can-i-prevent...
[ Parent
| on HN ]
Re:Open research, stronger privacy: Making Firefox users har...
by nneonneo on Wednesday November 11, 2026 @01:33PM
(#50456806)
[delayed]
Re:Open research, stronger privacy: Making Firefox users har...
by MayeulC on Wednesday November 11, 2026 @03:04PM
(#50457920)
[delayed]
Re:Open research, stronger privacy: Making Firefox users har...
by Sayrus on Wednesday November 11, 2026 @04:08PM
(#50458685)
Side-channels on such a model would be very hard to enforce: if any element of the page "moves around other elements", all other elements must be tainted as they'd leak information on the tainted DOM node. Presence or absence of a DOM node can leak information about a tainted context.
The second idea is vulnerable as well. As long as you can exfiltrate tainted data to untainted context, the protection will be quite weak.