4 ms·
WASM will be used to ship browser-in-browser runtimes (WebKit+FreeType already compiles to WASM) to make ad and tracking blockers impossible.
by tannhaeuser 10y ago
WASM will be used to ship browser-in-browser runtimes (WebKit+FreeType already compiles to WASM) to make ad and tracking blockers impossible.
- TomMarius 10y agoWhat's stopping you from not using such sites?
- tannhaeuser 10y agoIt's just that I find the WebAss propaganda dishonest and the discussion here naive. I personally have no problem discussing the economies of publishing, and I'm also not against ads. Tracking, OTOH, needs to go away.
- TomMarius 10y agoI don't see any propaganda, I see a very interesting, beneficial and good technology. What's naive about that? No one says it has no downsides; but some people don't consider it a downside. And again - if you don't like being tracked, there's nothing easier than not visiting these sites, because that's simply the price of visiting the page. Obfuscated JavaScript code is about as hard to read as equivalent WebAssembly code, maybe even harder, so you still have exactly the same options to find out you're being tracked.
- TomMarius 10y agoAnd I'd like to point out that tracking is very effective even with no JavaScript at all.
- eridius 10y agoWhy would that make ad and tracking blockers impossible? Those blockers usually operate by blocking resource loads, and a browser-in-browser runtime can't sidestep that, because any network access still has to go through the browser and therefore can be blocked.
- tannhaeuser 10y agoFair point. But a browser-in-browser can hide so many things from you. It can easily piggyback tracking data on regular content requests, use proxies, block basic page navigation; the possibilities are endless.