> If you have Internet access, NTP trivially gives you this. This is not always true, and the user is not always at liberty to change the clock settings on the

> If you have Internet access, NTP trivially gives you this. This is not always true, and the user is not always at liberty to change the clock settings on their device. > That's literally the point I addressed in the comment you replied to. Computers that are over 20 years old are still capable of connecting to websites using modern TLS. This is just not true. I do a lot of testing, and there are many devices as young as 5 years that cannot access some websites due to TLS incompatibilities. I have a very nice device that's 10 years old which I use daily that experiences this on a regular basis. > No, ever since ACME came out, certificate renewal can trivially be fully automated, with zero admin work required when one is about to expire. Automation breaks, and certificates expire. I encounter websites with broken certificates almost daily. > Which is trivially granted as long as you actually own the domain you're trying to get the certificate for. It is not trivial at all. It requires a lot of administrative work, and many people around the world do not have access to this process at all. > This is like saying that it's dangerous to go outside because there have been real cases of people being killed by meteorites. No, it is like saying there are people out there who want to access information on the device they have access to, and we should enable them to access that information as much as possible.