lovely

@Jes Inb4 you notice it's half a second off so it doesn't change the same instant.

@Jes not sure if it is still the case, but for a while time.is was behind by about 90ms

@Jes i love when clocks are perfectly in sync though

@kemona_halftau says my pc clock is 0.7s behind
but still considering this is a cheap LCD clock I don't think it will be that big of an issue

@kemona_halftau okay time.is is a couple seconds behind
unacceptable

@kemona_halftau just synced to NIST instead :3

@Jes i wonder if it is possible to sync a computer to the wwvb longwave timecode transmission signal at 60khz, which in theory could be received through a computer’s microphone port with nothing connected due to interference if recording at a high enough sample rate (anything above 120khz)

@kemona_halftau wait time.is uses nist
I guess windows time is behind

@kemona_halftau NIST is years out of date as is the fashion for US-based government entity

@kemona_halftau okay doing a manual sync directly to NIST still has a latency of -0.673s
thanks microsoft for not building in a latency compensation of any type

@kemona_halftau it was the same using the windows timeserver too, so this must be either my system having the latency or more likely windows itself being behind.

@Jes @kemona_halftau on pissnet it was always the one windows server that had a clock that was consistently off by a few seconds (IRC requires accurate time on servers because timestamps are used to resolve nick/channel collisions)

@Paradox Seems pretty accurate to me

@noisytoot @kemona_halftau back when I dualbooted linux and windows I ended up having a batch script that resynced the time
I know there was a fix to set windows to UTC but idc