@eff the whole point to the #HTTPSEverywhere db is to skip the lag of attempting a fetch that will potentially fail. This new version will require people to fetch the javascript file, execute it, then do another network fetch to check the site. How is that better than a browser that just tries HTTPS outright and reverts to http when it fails?