If it ever happened on a plane, then it means that the maintenance was intentionally skipped.
And that would of course never happen.
Especially since Firefox' certificates are hard-coded. Good luck removing untrustworthy CAs without recompiling the sourcecode.
That's easily done through the Certificate Manager.
How many hosting providers can you name that will install arbitrary certificates and run HTTPS for you without additional charges? GoDaddy? (No) FatCow? (No) SiteGround? (No) HostGator? (No) BlueHost? (No) DreamHost? (No)
They will generally offer self-signed HTTPS for a backend interface (e.g. one without your domain name in it). All of them want you to pay a fee for the service of offering HTTPS on your own virtual domain (regardless of who signs your certificate).
I'm sure they will change their business model.
Not the same thing, wildcard helps in cases where multiple subdomains are being served by one server with only a single ip address. Since Let's Encrypt is currenly discussing wildcards, and its not looking good for them to actually support them, this would require servers to have an ip address per domain. If a server has more than 2 domains it is server, its COMPLETELY unreasonable.
It's not necessary to have an IP address per cert anymore since every browser has support for SNI nowadays.
If my website just serves up public data that I don't care about the government seeing, you're going to disable new features on it anyway? Seems a bit extreme.
TLS can actually be used without encryption, the data is transfered in clear but you still get the authentication; which is actually something you want even if the data itself isn't secret.
More wildcard certs for me to buy.
If Let's Encrypt takes off, and it's fairly likely to do so given the sponsors they have (including Mozilla), you won't have to buy any certs at all. They will just be there automatically.
We failed to secure licenses from rights holders for the vast amount of music on the service.
But you still continued? Good plan there.