8 ms·
You say uMatrix is "somewhat more usable than NoScript, insofar as it usually allows Javascript on the local site by default, while automatically blocking JS on
by pmoriarty 10y ago
You say uMatrix is "somewhat more usable than NoScript, insofar as it usually allows Javascript on the local site by default, while automatically blocking JS on third-party domains"
But that's exactly the default I do not want. One of the main reasons I use NoScript in the first place is to protect against Javascript vulnerabilities. If the default is to enable Javascript, that defeats that protection.
- Dylan16807 10y agoYou can toggle it on both extensions.
- stephengillie 10y agoA more useful alternative may be disabling JavaScript globally, and maintaining a clearlist of sites allowed to run it. Or combine this with uMatrix, giving yourself a global blocklist with 3rd party granularity on the sites you do clearlist.
- stephengillie 10y agoWas this comment really so unhelpful as to merit a downvote?
- ryuuchin 10y agoYou can change this behavior in both NoScript and uMatrix. In uMatrix all you have to do is disable first party scripts in the global (*) profile. NoScript defaults to the opposite (don't allow any scripts) but the behavior can be changed to allow first party scripts by default.
- Houshalter 10y agoHow do I disable scripts for just one site? I tried to use uMatrix once as it was suggested as the alternative of noscript for chrome. I just wanted to get rid of those annoying anti-adblock popups on wired.com. However every setting I tried on the drop down menu failed to block javascript, or just blocked all content on the domain wired.com. I tried going deeper into the settings but I found the user interface confusing and nothing was labelled. It's definitely not a convenient alternative for noscript/javascript blocking. Even if it may be possible to achieve that with it.
- anc84 10y agoMake the script column for the host you want to block red/blue. Then make sure to save if it worked as intended.
- copperx 10y agoHow much of the 2016 Web is usable without JS?
- actsasbuffoon 10y agoA pretty good amount. For instance, HN is barely degraded at all. Voting causes a full page refresh, but that's about it. Some news organizations implement their paywalls with JS. It gets rid of a lot of annoying ads and scroll-behavior modifications. It actually makes some sites subjectively better.
- JoshTriplett 10y ago> For instance, HN is barely degraded at all. HN isn't the 2016 web at all. Not that you fundamentally need JavaScript, but HN's HTML hearkens back to the pre-CSS table-driven web.
- nickpsecurity 10y agoMost of the time you just enable the scripts with domain name and "cdn" in them. Sometimes, it's trial and error to find the fight combo but I usually get it in first guesses. I've found that the sites that were too much ttouble I just skip, momentarily irritated I didnt see the content, and then forget about that site. I can't say Ive lost anything major boycotting the worst offenders.
- zerognowl 10y ago> HN isn't the 2016 web at all. Yes but when visiting a website with JS turned off, the site can still be progressively enhanced similar to how an electric stairs still works when the power is switched off. Users of the stairs still get to climb it, but now they have to put in extra effort.
- JoshTriplett 10y ago> Yes but when visiting a website with JS turned off, the site can still be progressively enhanced similar to how an electric stairs still works when the power is switched off. It can, but sites often don't test that path (if they develop it at all), because it only applies to people who intentionally disable JavaScript. Once upon a time, screen readers and similar accessibility software didn't work well with JavaScript, so better sites would pay attention to that case for accessibility. However, screen readers work fine with standard browsers and JavaScript now, which makes the "JavaScript disabled" case an incredibly tiny fraction of web users. (In fact, Mozilla found a few years ago that there were far more users with JavaScript accidentally disabled than people who actually wanted it disabled.) So, handling disabled JavaScript by just saying "you seem to have disabled JavaScript; you should fix that" really does seem appropriate for the proportional amount of time worth spending on that tiny subset of users. That said, know your target audience. If you're building a mainstream consumer product, the proportional amount of time worth spending on running with JavaScript disabled rounds to zero. If you're building a product catering to a smaller subset of users, and you expect people with JavaScript disabled to represent a much larger fraction of your potential users, by all means take the extra development time to make that case work well.
- unethical_ban 10y agoSecurity is a sliding scale. I could stay home all day and wer big pads with sirens on saying "DONT TOUCH ME", but I choose to drive a car at 70mph, walk along-side busy roads and load 1st party JS from sites. My rationale is that I've chosen to go to a site, and most JS dangers are served from ad networks and trackers. Not typically from the site itself.
- blowski 10y agoI let JavaScript run, but not by default, so it's like "before getting in someone else's car for the first time, I check the brakes work before going 70mph". Of course, as long as we don't try to force our preferences on each other, we can both browse the web however we like.
- gorhill 10y agoOther default settings in uMatrix: uMatrix comes with many hosts files enabled[1], so even if working in allow-all/block-exceptionally, most trackers/ads and whatnot will still be blocked. There is no pre-whitelisted (aka "trusted") 3rd-party hostnames in uMatrix, that will be for you to decide. The default in uMatrix, in full view in the popup panel, can be changed with a few clicks from the main popup panel, and you can also remove all the default whitelisted hostnames in NoScript. [1] entries are translated into `* hostname * block`.
- coldtea 10y ago>One of the main reasons I use NoScript in the first place is to protect against Javascript vulnerabilities All 0 of them?
- SquareWheel 10y agoYou've received downvotes, but you're not wrong. Javascript security used to be a concern, but that's been effectively eliminated with modern browser design. Code is sandboxed, processes are isolated, OS-level security is used on top of that. The few CVEs that show up are reported quickly via browser bounties or in-house testing. People claim bounties are ineffective, but how many exploits have we really seen emerge from "black markets" or other sources? I ran without JS for a few years and then realized it was making my online experience more miserable than it needed to be. I can't remember the last time I actually saw a computer "infected" just from visiting a website, and not through social engineering. Can you? The bottom line is that the margin for being compromised via JS is so small that it might as well not exist. If you disable it because privacy or surveillance or whatever else, that's your prerogative. But the security issue is completely overstated and largely misinformed.