... | ... | @@ -60,7 +60,7 @@ If a resource cannot be fetched locally and Decentraleyes is instructed to allow |
|
|
|
|
|
They show up when both extensions are attempting to redirect a specific request. The race is always won by the most recently installed extension. This is why recent versions of Decentraleyes automatically set up secure connections when forced to let intercepted requests through.
|
|
|
|
|
|
This means that it's safe to disable HTTPS Everywhere for supported CDNs, as long as you're using a recent version of Decentraleyes _(1.3.7.1 and up)_. Doing so should prevent further warnings and conflicts. Follow this [short guide](https://decentraleyes.org/configure-https-everywhere/) to configure your installation of HTTPS Everywhere.
|
|
|
This means that it's safe to disable HTTPS Everywhere for supported CDNs, as long as you're using a recent version of Decentraleyes _(1.3.7.1 and up)_. Doing so should prevent further conflicts, and warnings. Follow this [short guide](https://decentraleyes.org/configure-https-everywhere/) to configure your installation of HTTPS Everywhere.
|
|
|
|
|
|
##### Will it work well in combination with other privacy enhancing add-ons?
|
|
|
|
... | ... | |