Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
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

Closed

Description

@User486375

Type: feature request

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.

Activity

  1. pipboy96 commented on Mar 8, 2019

    @pipboy96
    Contributor

    Do you mean "Disable HTTPSe on this website" should be replaced with "Disable EASE on this website"?

  2. User486375 commented on Mar 8, 2019

    @User486375
    Author

    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.

  3. pipboy96 commented on Mar 8, 2019

    @pipboy96
    Contributor

    @User486375 By default only stable rules are enabled already.

  4. User486375 commented on Mar 8, 2019

    @User486375
    Author

    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.

  5. zoracon commented on Mar 14, 2019

    @zoracon
    Contributor

    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?

  6. added
    EASEEncrypt all sites eligible (#16985)
    on Mar 14, 2019
  7. pipboy96 commented on Mar 14, 2019

    @pipboy96
    Contributor

    @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.

  8. sirald66 commented on Mar 25, 2019

    @sirald66
  9. pipboy96 commented on Mar 25, 2019

    @pipboy96
  10. sirald66 commented on Mar 25, 2019

    @sirald66
  11. pipboy96 commented on Mar 25, 2019

    @pipboy96
  12. Bisaloo commented on Mar 28, 2019

    @Bisaloo
    Collaborator

    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.

  13. pipboy96 commented on Mar 28, 2019

    @pipboy96
    Contributor

    @Bisaloo EASE has a differently looking HTTPS Everywhere icon. Not sure how it's possible to not notice it.

  14. mikhaelkh commented on Jun 4, 2019

    @mikhaelkh

    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.

  15. self-assigned this
    on Nov 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

EASEEncrypt all sites eligible (#16985)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions