Hmmmm ... Does this mean "HTTPS Everywhere" is no longer needed?[1]
And, of course, it freaks out with the previously saved self-signed cert installed on my WiFi router. ... sigh
The assumption that whatever is being served on :443 is HTTPS with the same content as what is being served on :80 HTTP is wrong. It might practically be true >99% of the time, but some websites will still break for no good reason.
Probably not quite - I can't easily find an exact reference, so take with a grain of salt, but my recollection is that HTTPS Everywhere includes some slightly more sophisticated transforms (ex. for annoying sites that serve http://www.site.tld but HTTPS on https://secure.site.tld).
It's not as powerful/flexible/configurable, but certainly ticks some of the boxes.
Ah yes, I don't want anyone to eavesdrop on my pr0n!
Edit: to clarify, I find it weird that this has been limited to Private Browsing, when most people don't even use it for anything but adult websites. The feature is good and should be available for regular browsing too.
It can be enabled for all windows, but it was not enabled at all when the feature was first rolled out in v83. Presumably they wanted to allow time for any bugs to be shaken out before imposing it by default in any circumstance. It seems plausible they could enable it in regular windows as well in the future.
That way they can roll it out to all Firefox users, and if something breaks, users can always fall back to non-private mode until it's fixed.