4 ms·
Mostly yes: I use JS-blocking browser extensions, which (mostly) offer domain-by-domain control over JS loading. And only enable JS when the risk/reward ratio
by bell-cot 4y ago
Mostly yes: I use JS-blocking browser extensions, which (mostly) offer domain-by-domain control over JS loading. And only enable JS when the risk/reward ratio seems low enough.
Between the browser security issues & resource usage, anti-improved speed & UX, etc. - enabling JS is mostly not worth it to me.
(Yes, doing this kinda rules out a fair number of web sites for me. But with ~10,000x more content on the web than I could view in my remaining mortal years anyway...ruling out a lot of sites is a feature, not a bug.)
- jotm 4y agoWhich one? I used NoScript but on Firefox it always reblocked all allowed domains after reopening the browser. It used to work fine years ago, and some people say that's not normal behaviour, but I've stuck with it for a few versions and got sick of it. Honestly, just an ad blocker is enough.
- bell-cot 4y agoAt the moment, NoScript on FF actually. With how few domains I load the JS from, the "reblock after reopen" behavior is 60/40 feature/bug for me.