Hi The easiest way is to make a pull request on Github. You can find all the rules here: https://github.com/EFForg/https-everywhere/tree/master/src/chrome/content/rules There are a lot, so I recommend to use the search function.
If you are already familiar with Git, you can clone the repository. Otherwise you can sign up and then you are able to just edit a file (make sure that you are on the master branch). Github will make a fork and a pull request automatically. Please switch always back to the master branch before editing a new rule, so Gihub will create a new pull request for each change. regards Jonas Am 09.04.15 um 15:56 schrieb Alexander Buchner: > I wanted to reenable some rules and know that I have to delete the > 'default_off'-tag in the .xml, but this is not sufficient I think. > There has to be another location where this information is stored, > i.e. when I visit the site for which I just edited the rule the rule > still doesn't apply and I can see this in the httpsE menu button. I > know that I can manually enable the rule through the menu but this > would only affect me. I want to change it in the source so that the > rule gets deployed enabled in the next release. > > So, where in the source can I do this? > _______________________________________________ > HTTPS-Everywhere mailing list > [email protected] > https://lists.eff.org/mailman/listinfo/https-everywhere _______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
