I sympathise with the sentiment of this post and admit things can and should be better. But there are a few points to be made: > the situation hasn’t changed a

I sympathise with the sentiment of this post and admit things can and should be better. But there are a few points to be made: > the situation hasn’t changed and if it worked last time it should still work this time The situation has changed though - who knows what vulnerabilities had to be addressed in any of the dependencies or the protocol. Just because you forgot about it doesn’t mean others did. I’m not a fan of automated software updates and believe they should be restricted to just essential security patches (where the risk of a vulnerability is greater than the potential to break a system) > You would not have known this unless you interacted with Letsencrypt on a daily basis, but like most of these things their whole value lies in NOT having to interact with them all the time. There’s plenty of stuff that we interact with on an infrequent enough basis that we can get caught out when something changes and we realise we didn’t know and maybe had little way to know. This is just impossible to avoid in the real world. The only way to address it is better communications. I generate my LetsEncrypt certs in docker containers mainly because of all the dependencies and that it’s clear it’s still evolving. Maybe in 10 years time it’ll be as mature as a nix shell command like ‘ls’.