2 ms·
The only way to fight that is to, as a community, refuse to run _all_ wasm that is found to serve ads, or infringe on privacy, or exhibit other malware traits.
by dotancohen 4y ago
The only way to fight that is to, as a community, refuse to run _all_ wasm that is found to serve ads, or infringe on privacy, or exhibit other malware traits.
The only way to do that would be to use browser extensions that disable and report, to disable for other users automatically. But how would we identify the executables? hash? That can be changed trivially.
I really fear that wasm brings us 180 degrees from "don't execute anything from the internet" to "all WWW usage is running other peoples' executables".
- deleted 4y ago[deleted]
- jschrf 4y agoThat's already the case! Also, having other people tricked into running other-other people's code with the others' credentials against _your_ code. I think WASM will actually be more secure than the exsting www model. See: POST for an example :) I agree though... there will be bad actors and an ever evolving cat and mouse game