https-everywhere VS AmIUnique

What's the issue with Firefox's implementation? And this doesn't change the fact that HTTPSe is literally fully sunset.

Here's a small historical curiosity: In HTTPS Everywhere, the functionality used to be call "Block all HTTP requests" but when that functionality was changed (back in 2016 [0]) to not block connections to non-HTTPS hidden services, it was renamed to "Block all unencrypted requests".

I just checked, and indeed Tor Browser 11.5 does not block non-HTTPS connections to hidden services, even when in "HTTPS-Only" mode. Thankfully.

[0]: https://github.com/EFForg/https-everywhere/pull/4370

HTTPS Everywhere is discontinued by its creator and will be removed completely next year, because every major browser includes the functionality already anyways.

HTTPS Everywhere Chrome Web Store Github

[1] https://github.com/EFForg/https-everywhere/tree/master/src/chrome/content/rules

You should ask those writers or see if you find anything useful at their github page here

It's a ruleset for the HTTP Everywhere browser extension.

Maybe try upstream at https://github.com/EFForg/https-everywhere

I go the opposite way. I trust a company that takes my money to pay its costs to keep my privacy. As opposed to a company who "doesn't know who I am". (Apart from unique fingerprint https://amiunique.org/ over many queries over many months)

You're not completely wrong, but that ship has sailed a long time ago: https://amiunique.org

Until browser fingerprinting is addressed, there will be no real privacy.

You are. Compare the fingerprints of your two browsers: https://amiunique.org, https://coveryourtracks.eff.org. Very likely, the fingerprints are very similar. For anonymity, use Tor.

Browser Fingerprint Checker

Guarda qua: https://amiunique.org/

It’s mostly client-side stuff, you can access browser’s properties like canvas size, plugins, hardware, sensors. Try visiting https://amiunique.org/ You’ll get the idea.

https://amiunique.org/

https://coveryourtracks.eff.org/