Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upOption to downgrade to stable rules while EASE is enabled #17554
Comments
This comment has been minimized.
This comment has been minimized.
|
Do you mean "Disable HTTPSe on this website" should be replaced with "Disable EASE on this website"? |
This comment has been minimized.
This comment has been minimized.
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 |
This comment has been minimized.
This comment has been minimized.
|
@User486375 By default only stable rules are enabled already. |
This comment has been minimized.
This comment has been minimized.
|
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. |
This comment has been minimized.
This comment has been minimized.
|
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
added
the
EASE
label
Mar 14, 2019
This comment has been minimized.
This comment has been minimized.
|
@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. |
This comment has been minimized.
This comment has been minimized.
sirald66
commented
Mar 25, 2019
|
I may not fully understand the issue, but is this an example? - https://qpages.com/ With EASE enabled, the icons break and their labels overwrite the text making them unreadable. |
This comment has been minimized.
This comment has been minimized.
|
@sirald66 This page has mixed content issues that are unrelated to EASE. Same thing happens if strict MCB is enabled in browser settings. |
This comment has been minimized.
This comment has been minimized.
sirald66
commented
Mar 25, 2019
|
@pipboy96 I've novice in this area. What/where would this MCB setting be in Chrome? |
This comment has been minimized.
This comment has been minimized.
|
@sirald66 |
This comment has been minimized.
This comment has been minimized.
@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. |
This comment has been minimized.
This comment has been minimized.
|
@Bisaloo EASE has a differently looking HTTPS Everywhere icon. Not sure how it's possible to not notice it. |
User486375 commentedMar 8, 2019
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.