>the entire point is that making all request come from the same source - which can happen in more opaque way with obfuscated WebAssembly. No matter how convol

>the entire point is that making all request come from the same source - which can happen in more opaque way with obfuscated WebAssembly. No matter how convoluted the WebAssembly bytecode, the browser engine still has to execute it and therefore it will ultimately know to go fetch "something" from AdsClearinghouseProxy.Com. If the browser engine knows that fact, the ad blockers know that fact as well. In that aspect, it doesn't matter whether the string "AdsClearinghouseProxy.Com" is obvious in plain-text Javascript or hidden in WebAssembly bytecode. >technologies like WebAssembly. I just think that it's a bad idea to underestimate the ingenuity of people that see dollar signs when they look at a new tool. It's not a technology problem and WebAssembly won't help the advertisers as much as you think. Check out the questions asked in that reddit thread. The advertisers already have the technical tools and know-how to do something about "empty ad boxes" when ad block is active. Nevertheless, they don't pursue the solutions. The issue is that they want to have their cake and eat it too. WebAssembly will not remove the immense friction of coordinating all entities to deliver merged ads that are undetectable by ad blockers.