4 ms·
> We cant ban just the bad Javascript Well, technically it's possible, and even some parts of the script could be allowed to run or not. > a browser cannot di
by snaky 8y ago
> We cant ban just the bad Javascript
Well, technically it's possible, and even some parts of the script could be allowed to run or not.
> a browser cannot distinguish it from the good
But the user can. And the machine could help, thanks to machine learning.
- JohnFen 8y ago> But the user can. How? I don't think that users even agree what consists of "good" and "bad" JavaScript.
- snaky 8y agoFor the simplest possible example, ask any Noscript extension user. For the more advanced things, like identifying the part of Javascript code that brings e.g. 'the fancy eating 40% of the CPU scrollbar' user want to disable, some automation is needed.
- JohnFen 8y agoI am a NoScript user. I use it to block all JS by default. If a web site won't work properly that way, and the site is somehow really important, I'll work out what the minimum scripts necessary to let the site do what I need is, and just allow those. If the site isn't somehow critical, I just don't use the site. I have to do it that way because it's very difficult to determine which scripts are bad and which aren't without actually reviewing the JS itself. In my view, "bad" usually means that the script is phoning home in some way.
- anoncake 8y agoConsider Javascript that replaces native browser functions. Web pages that are essentially static documents, but still dont work without Javascript. Is this good Javascript? I dont think so. Does disabling it on an individual level help? No.