On Fri, 31 May 2013 12:33:29 Paul Wise wrote: > I always wondered why the plugin was bundled with a snapshot of data > that by definition is continuously changing. Would it not be better > for the plugin to ship with a snapshot of data and then automatically > update it as needed? Or push this out into DNS or something else.
I'm with you Paul as indeed separating volatile data and the plugin code makes perfect sense. I doubt the importance of receiving frequent updates to "https-everywhere". Surely I do not visit most of the eleven thousand web sites covered by its rules and for small subset of those web sites that I visit I'm not sure if I would welcome any sudden and unexpected changes introduced by update. There is a lovely "https-everywhere" companion plugin maintained by yours truly: "https-finder". It probes any web site for HTTPS and allows one to easily create a rule for "https-everywhere". So I can control whenever I want HTTPS by default on the sites that I visit often and for other web sites there is an automatic HTTPS detection which IMHO makes frequent updates to "https-everywhere" not that important as long as the latter is accompanied by "https-finder". Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B --- I do not fear death, in view of the fact that I had been dead for billions and billions of years before I was born, and had not suffered the slightest inconvenience from it. -- Mark Twain
signature.asc
Description: This is a digitally signed message part.