https-everywhere VS SponsorBlock

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

just use sponsorblock today, works fine on all my devices. https://github.com/ajayyy/SponsorBlock

from mobile phone to tv to pc.

You are one of today's 10,000.

https://sponsor.ajay.app/

And if you have android:

https://github.com/polymorphicshade/Tubular

The SponsorBlock [0] addon has already solved that for sponsored/ad segments in videos. Rather than AI, crowdsourced timestamps lets it automatically skip past adverts.

[0] https://sponsor.ajay.app/

For integrated ads on YouTube (sponsor messages), you can use the SponsorBlock extension (https://sponsor.ajay.app/). If you're using Android, you can also get NewPipe with SponsorBlock integration.