You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Option to downgrade to stable rules while EASE is enabled #17554
Rather than disabling the extension entirely to access non HTTPS sites, users should default to stable rules and also be able to downgrade to them just like the option Disable HTTPS Everywhere on this site. This would be especially useful on sites which are partially HTTP.
Do you mean "Disable HTTPSe on this website" should be replaced with "Disable EASE on this website"?
No, because users may still want to have that option while EASE is enabled if stable rules break a site, I think this should be in addition to it but only an option while EASE is enabled. As for when users choose to visit the HTTP version of a site the default should be Disable EASE.
I'm saying when a user clicks to visit an HTTP site with EASE enabled, the default behavior should be disabling EASE but they should still have the option to fully disable the extension for that specific site if need be.
I'm trying to understand this request more. How is this more beneficial than unchecking EASE, since in "normal" mode stable rules will apply and allow you to navigate to HTTP sites?
@zoracon They want to use EASE for all website except one or two that still do not support HTTPS. These websites likely reference other websites that can be rewritten to HTTPS. They want to rewrite as many requests as possible.
I'm trying to understand this request more. How is this more beneficial than unchecking EASE, since in "normal" mode stable rules will apply and allow you to navigate to HTTP sites?
@zoracon if you disable EASE, you have to reactivate it afterwards (and it's easy to forget). That does not happen if you simply add an exception for a given domain.
I want to use "encrypt everything" by default, and when it breaks the site, I don't want to completely disable HTTPS Everywhere on the site straightaway, first I want to apply rulesets on the site. And if rulesets are breaking the site, only then I want to disable extension on the site until the ruleset issue is being resolved.
There's 3 possible states of HTTPS Everywhere: encrypt everything, apply rulesets, disabled. But only 2 of them are available at any given moment: either rulesets & disabled or encrypt everything & disabled.
And only one custom site list exists - for disabled sites.
Consider Chrome's implementation of Cookies - chrome://settings/content/cookies. There's also 3 states for each site: allow, clear on exit, block. Chrome maintains 3 custom lists - a list for each state.
Activity
pipboy96 commentedon Mar 8, 2019
Do you mean "Disable HTTPSe on this website" should be replaced with "Disable EASE on this website"?
User486375 commentedon Mar 8, 2019
No, because users may still want to have that option while EASE is enabled if stable rules break a site, I think this should be in addition to it but only an option while EASE is enabled. As for when users choose to visit the HTTP version of a site the default should be
Disable EASE.pipboy96 commentedon Mar 8, 2019
@User486375 By default only stable rules are enabled already.
User486375 commentedon Mar 8, 2019
I'm saying when a user clicks to visit an HTTP site with EASE enabled, the default behavior should be disabling EASE but they should still have the option to fully disable the extension for that specific site if need be.
zoracon commentedon Mar 14, 2019
I'm trying to understand this request more. How is this more beneficial than unchecking EASE, since in "normal" mode stable rules will apply and allow you to navigate to HTTP sites?
pipboy96 commentedon Mar 14, 2019
@zoracon They want to use EASE for all website except one or two that still do not support HTTPS. These websites likely reference other websites that can be rewritten to HTTPS. They want to rewrite as many requests as possible.
sirald66 commentedon Mar 25, 2019
pipboy96 commentedon Mar 25, 2019
sirald66 commentedon Mar 25, 2019
pipboy96 commentedon Mar 25, 2019
Bisaloo commentedon Mar 28, 2019
@zoracon if you disable EASE, you have to reactivate it afterwards (and it's easy to forget). That does not happen if you simply add an exception for a given domain.
pipboy96 commentedon Mar 28, 2019
@Bisaloo EASE has a differently looking HTTPS Everywhere icon. Not sure how it's possible to not notice it.
mikhaelkh commentedon Jun 4, 2019
I want to use "encrypt everything" by default, and when it breaks the site, I don't want to completely disable HTTPS Everywhere on the site straightaway, first I want to apply rulesets on the site. And if rulesets are breaking the site, only then I want to disable extension on the site until the ruleset issue is being resolved.
There's 3 possible states of HTTPS Everywhere: encrypt everything, apply rulesets, disabled. But only 2 of them are available at any given moment: either rulesets & disabled or encrypt everything & disabled.
And only one custom site list exists - for disabled sites.
Consider Chrome's implementation of Cookies -
chrome://settings/content/cookies. There's also 3 states for each site: allow, clear on exit, block. Chrome maintains 3 custom lists - a list for each state.