Ruleset bloat -> memory usage, startup time. Replace by HTTPSF
Problem: HTTPS Everywhere consumes over 30MB of RAM according to WMI and over 10MB according to about:memory. Startup time is noticeably slower.
Cause: The default ruleset is absolutely massive, over 3MB in XML.
Suggestion: Remove the default ruleset. Create a tighter cooperation with HTTPS Finder to compensate, or even implement HTTPSF's functionality into HTTPSE.
Reasoning:
- same problem as with Adblock Plus' Easylist and everything else based on community rules that are stored client-side: 99.99% goes unused and only bogs down the client without ever being useful to an individual user. Messy, inefficient and not very helpful since a lot of users' regular sites are not in the ruleset anyway.
- replacing the rulesets by a cooperation with HTTPS Finder means that users will have ONLY the rulesets for the sites they themselves visit, making the ruleset 100% efficient at the measly cost of a single button click per new website.
In fact, why not just integrate HTTPS Finder (or its functionality anyway) into HTTPSE? And while you're at it, why not upload it to AMO so we can get updates and everything?
HTTPSF broke in the latest Firefox/Palemoon and there hasn't been any activity on the code to fix it for 3 months. HTTPSF not working means HTTPSE not working for many people who surf a lot. Essentially, HTTPSE partially depends on HTTPSF on the user end. Merging the two improves the reliability of the entire concept.
Please consider, I miss these 2 a lot but HTTPSF does not work and HTTPSE is just a bloaty mess right now.
Trac:
Username: Faziri