it's in trying to resolve problems later on, when you'll find that systemd helps you obscure the source of the trouble instead of resolve it.
Obscured in what way?
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.
Say "twenty-three-skiddoo" to logout.