>>884970
Maybe they are compromising so normalfags who are accustomed to faceberg, Jewgle and twatter can get right into browsing using Tor? I praise the Tor project for spreading it to the masses, but I am critical of their choice of enabling JavaScript by default. People don't use the Torbrowser to pay their bills, they use it to visit sites without allerting spooks to WHAT they are looking for. So if a website refuses to load because muh JS backdoor the appropriate choice would be to either not use the site at all OR selectively enable which scripts are enabled AND make sure they have access to NOTHING interesting, but see below why that might be a mistake.
Unlike web 2.0 cancersites, Tor Project takes the issue of JavaScript seriously, understand it has its downsides and has publisised a defence of default enabling: https://www.torproject.org/docs/faq.html.en#TBBJavaScriptEnabled
On why selective enabling of scripts is a bad idea, the Tor project has the following to say:
<There's a tradeoff here. On the one hand, we should leave JavaScript enabled by default so websites work the way users expect. On the other hand, we should disable JavaScript by default to better protect against browser vulnerabilities ( not just a theoretical concern!). But there's a third issue: websites can easily determine whether you have allowed JavaScript for them, and if you disable JavaScript by default but then allow a few websites to run scripts (the way most people use NoScript), then your choice of whitelisted websites acts as a sort of cookie that makes you recognizable (and distinguishable), thus harming your anonymity.
They have also written on how to disable JS: https://www.torproject.org/docs/faq.html.en#DisableJS
<The more klunky way to disable JavaScript is to go to about:config, find javascript.enabled, and set it to false.
tl;dr: Tor project enabled JS by default in Torbrowser to appease normalfags, but disabling it is trivial to someone with 3 braincells.