Wow, very interesting read, thanks for sharing this! I hope they find a fix for this soon!
I think you’ll find this plugin more useful than the NoScript plugin - https://www.mywot.com/. It shows a trust factor/rating next to links before you even click on them. Plus you can use their APIs in your own web app to protect your users too. A very good alternative, in my opinion.
90% and 2% – how did you arrive at those numbers? Please cite. Else, please refrain from cooking up data.
In his talk, Mike Gerwitz does a good analysis of these problems. Do watch it when free.
The community-powered approach enables WOT to protect you against threats that only the human eye can spot such as scams, unreliable web stores and questionable content. It complements traditional security solutions that protect computers against technical threats such as viruses and other harmful software.
mywot is about human detectable threats. It is meant only to complement traditional security solutions, not replace them. So, mywot is not in the same domain as noscript, and is hardly a replacement for it.
Besides, I don’t feel too comfy about building my entire security model against the APIs of one company.
My bad. Wasn’t trying to cook up data, but I did mis-interpret a piece of information from here, which mentioned something about approximately 12% of JS libraries having a vulnerability. I take back the statement made earlier. Apologies.
Of course, I never implied building the entire security model just using their APIs alone, no competent developer would do so. That would be foolish.
And that’s the reason I still maintain that blocking JS altogether on most of the sites that a person visits seems like a temporary fix than addressing the real issue. My take on this, anyway.
I appreciate the effort taken to reply, and thanks for the links Was a good read.