3 ms·

That's interesting, I wasn't aware of "navigator.sendBeacon" before. Question about the user script. Blocking WebSockets I can understand as they can be used f

That's interesting, I wasn't aware of "navigator.sendBeacon" before. Question about the user script. Blocking WebSockets I can understand as they can be used for exfiltrating data you don't want them to get a hold of. But why disable WASM? It can't be used for exfiltrating, and disabling it probably gives them a stronger data-point than just leaving it on, for when they are able to exfiltrate data (via CSS HTTP requests for example).

varenc 5y ago
Oh I don't actually disable WASM. Those are just different scripts that can apply to pages when a filter matches. I disable sendBeacon everywhere with `*##+js(disable-sendBeacon.js)` but the others I don't use or only use on a specific site. I believe I added the WASM removal just to test how a particular site's fallback would work when it wasn't present. That said, disabling WASM probably reduces your browser fingerprinting bits. I bet fingerprintjs[0] uses it. UBO already has a built-in set of powerful scripts[1], but I just wrote my own for fun. I think I could have done this by just using the built-in ones. edit: This filter does the same thing just using the built in `set` script, but won't log to console: *##+js(set, navigator.sendBeacon, trueFunc) [0] - https://fingerprintjs.com/demo/ https://fingerprintjs.com/demo/ [1] - https://github.com/gorhill/uBlock/wiki/Resources-Library https://github.com/gorhill/uBlock/wiki/Resources-Library