7/6/2026 at 4:41:26 PM
by Asmod4n
7/6/2026 at 5:01:55 PM
Systems are absolutely not ready. Leap seconds are a bad idea and negative leap seconds are worse. Just don't do it and let the drift cancel out.by wmf
7/6/2026 at 5:27:04 PM
Google's proposal is a smear. [1] Most time servers do not use smear. No idea what behavior it may introduce in places where sub-second time is important. Curious if all these bugs [2] were fixed specifically to deal with going backwards.by Bender
7/6/2026 at 4:54:18 PM
NTP.By any other standard, most manually set clocks are up to a full minute off all the time.
by d00d0ff000
7/6/2026 at 7:42:46 PM
Yeah, but we're thinking of systems where nanoseconds matter.MiFID 2 alone forces sub-μs precision. Million times less than the leap 1 second.
NTP minute away is good for displaying date on the workstation, not for many of the devices that are critical to the modern world.
by subscribed
7/6/2026 at 7:43:55 PM
dont most systems that rely on sharp timing simply manage it themselves.by cyanydeez
7/6/2026 at 8:02:34 PM
Yesno.Sure they have their own time servers fed from the GPS, but they need to be _accurate_ in relation to the world.
But timestamps used by companies forced to use very accurate timing must be synchronised to UTC.
by subscribed
7/6/2026 at 6:34:55 PM
[flagged]by rezvovmobile