[harrygallagher4]

I think about this too. uBlock origin is already running into issues with trackers disguising themselves as first-party, what about when those trackers are genuinely first-party, and bundled with the page's js (which you can't just outright block)? What happens when those trackers are bundled and compiled to wasm along with the sites js? Do we then analyze the wasm and try to guess which parts are necessary for a site to function and which parts are the tracking?

I'm not trying to be overly cynical here, all of these topics remind me of high school when I'd download mildly-sketchy executables, decompile them, and try figure out whether or not they were safe to run. I would love to poke around with reverse engineering wasm, but I'd rather not have to do that every time I visit a new website.

[BlueTemplar]

And this is why if blocking the "web"site JavaScript breaks the "web"site itself, then it never was a website to start with!

(Trackers using these kinds of tactics was only a matter of time between trackers and blockers...)

[Shish2k]

How I wish the problem were only breaking the "web" - these days, blocking tracking scripts on my router ends up breaking my desktop applications...

(Example of the day, Parsec; example from yesterday, NVidia's driver-update software :( )

[marcthe12]

Just wow. I won't be surprised if doing something like that will break the os.