|
|
|
|
|
by eh_why_not
651 days ago
|
|
No-JS user here. A disturbing trend noticed in the past two months: can't login anymore to some financial/health services sites (bank/insurance/etc) without disabling all of NoScript - no amount of selective enabling of websites satisfies them, and those websites are using known infractors like Adobe. In other words, there is code in the backend checking that all tracking/-ware has run on the browser, and refusing to let you login unless you let it all run, while none of it is necessary (as evidenced by older versions - and other sites - accepting only the top site being JS-enabled). "We either track the living shit out of you, or you don't access the essential services you need, even though technically it is not needed." |
|
Things like this are why I worry a bit about the proliferation of things like WASM, while JavaScript isn't great, it actually gives a great amount of control to the end user, to both see, understand and the ability to actually modify what is running in their browser. With WASM, all of this becomes highly impractical. Instead of a (semi-)readable, modifiable block of interpreted code, with the ability to inspect and modify the state at almost arbitrary points, you just get opaque binary blobs that you basically can't do anything with. As more and more sites switch to using compiled WASM blobs for their logic, it will become increasingly difficult to observe or modify any behavior of these websites as an end user.