@nixCraft We're pretty spoiled when it comes to time sources lately. Nearly everyone has an NTP or GSM synced clock in their pocket, and most of our devices sync too.
Remember when you had to call a phone number and listen for "AT THE BEEP THE TIME WILL BE”? Aiigh!
@nixCraft You do realize devices and computers have batteries to save the current time and that a drift of a second or so is not going to impact any of that... right? You act like without NTP, time is going to skew horribly on every single device randomly and unpredictably by hours or days.
And if your device's battery fails, you have bigger issues than just time drift.
NTP time sync is nice in certain situations, but it isn't the life-saving, critical service you make it out to be.
@thespiralcow @nixCraft For https are some minutes into the future already a problem. Different timestamps in the logs is also annoying, if you search for a problem.
It is not the end of the world, but in datacenters you can run into some nasty problems.
@nixCraft Remember folks. For the low, low price of some lost accuracy, you *can self host* your own time server (at stratum not 1), alongside that pi-hole you'd probably better be running in 2024..
anyway, two more cents from some random nerd. peace out.
@nixCraft not an NTP problem, per se, but the coin cell battery backup on my home server ran down. We had a power cut and ESXi failed to boot, along with all the VMs. Incorrect system time meant all the signed driver modules failed to auth and the system failed to boot.
Time is important.