12 ms·
Somehow I have the sinking feeling that the most popular "killer app" for webassembly will be circumventing user preferences like "never auto-play" - or thwarti
by musicale 6y ago
Somehow I have the sinking feeling that the most popular "killer app" for webassembly will be circumventing user preferences like "never auto-play" - or thwarting ad blockers.
- rlanday 6y agoIt’s long been possible to decode H.264 using JavaScript (which obviously uses way more power than the native decoder). This is why browsers only restrict audio playback rather than actually autoplaying video.
- jniedrauer 6y agoAfter playing around with immediate mode GUIs in WebAssembly, I can envision a future which renders any kind of content blocker obsolete. The internet could be turned into cable television. I don't want to sound overly pessimistic, but it seems very plausible that this is the future we will eventually end up with.
- maxkwallace 6y agoI worry a lot about this but if this is the price of competing with the Google/Apple duopoly maybe it's worth it.
- tmccrary55 6y agoWasm has a pretty simple execution model, wouldn’t be hard to write something that preprocesses wasm code during load, similar to what you can do with java classloaders.
- pjmlp 6y agoEasily preventable using encrypted wasm modules.
- drran 6y agoWe can handle Wasm like Flash: declare it obsolete and then reinvent it again.
- blackoil 6y agoDeclaring something obsolete doesn't make it so. Flash went away because of iPhone and rise of mobile app and still it took about a decade for it to be irrelevant. Without a similar tectonic shift, it would take longer.
- sam0x17 6y agoThe thing with WASM though is you can always intercept it at the edges where it interacts with the DOM. The usual ad blocking tactics of either deleting particular arrangements of DOM nodes, blocking specific js/wasm payloads, and blocking specific domain names will still be unaffected. The tactics don't even need to change.
- nyanpasu64 6y agoIf an entire UI (content plus ads) is drawn with wasm onto a canvas (the way Qt WebAssembly does it), it will be impossible to use CSS to hide ads, and possibly more difficult to modify the script to disable the ad-loading functions.
- CGamesPlay 6y agoGoogle would probably not feature you very high in search results, though, since your website has no indexable text.
- vbezhenar 6y agoIf this technique would become popular, Google will OCR it just like it runs JS.
- ath92 6y agoThis technique is essentially the same as websites made entirely in Flash back in the day. And back then, the only way to have Google index your site was to provide a separate (hidden) version that used normal, semantic HTML.
- emilsedgh 6y agoThey can use it only for video players that'll autoplay for example.
- anoncake 6y agoGoogle is an advertising company. It would make sure there is a way to get your site indexed, perhaps by providing an alternate machine-readable version just to them. As a bonus, that version would not be available to potential competitors.
- flohofwoe 6y agoWASM modules can be blocked by domain just like regular ads. Just block the whole thing, problem solved.
- tinus_hn 6y agoJust like you can easily set your browser to refuse all cookies. Problem solved, now you can’t browse half the internet.
- AgentME 6y agoWebAssembly doesn't grant any extra permissions into the inside of the browser sandbox. Audio and canvas HTML elements already exist and don't have any innate connection to WebAssembly. (If you ignore performance, WebAssembly could be entirely polyfilled into old browsers that didn't support it through a Javascript interpreter.)
- vbezhenar 6y agoIt's not about permissions. It's about decoding video using WebAssembly and rendering it on canvas. Browser can't prevent it. Now I'm not sure that it wasn't possible before WebAssembly... Decoding some tiny video should not be that resource-intensive. Also you could just utilize GIF.
- a1369209993 6y agoMore to the point, it's about decoding documents using WebAssembly and rendering that on canvas, thus circumventing browser-based discrimination between legitimate and malicious content.
- eis 6y agoIt is about permissions. You can autoplay video just fine with HTML5. But you can't do it with sound. And how would your WebAssembly decoded video play sound? Right, using the exact same HTML5 media elements. WebAssembly doesn't allow you to somehow do different things in the page. It only allows some computations but to actually have any output it has to resort to the same APIs that your normal JS uses.
- vbezhenar 6y agoIf you can autoplay html video without sound right now, then you're right, I thought that autoplay was forbidden for all videos.
- magicalhippo 6y agoThat's what I told Firefox, but for some reason video autoplays just fine all the time so...
- greggman3 6y agoThis already happened. It's why the Chromium team doesn't allow blocking video completely because they saw the advertisers just working around the issue by making custom players. Those players were bloated and heavy so by blocking video for the user they didn't actually help block video and they made the problem worse. So yes, with or without wasm, people will roll their own ways of trying to get your attention.
- flohofwoe 6y agoPlaying audio from WASM means going through WebAudio, there is no magic direct connection between WASM and the system's audio device.