this post was submitted on 16 Aug 2024
785 points (91.6% liked)
Memes
45738 readers
470 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Right! Just to prove a point, I am going to make an NTP enabled rolex, and sync it to my microsecond accurate local NTP server! :P
To be fair, I did have a watch that automatically synced itself to the us naval observatories atomic clocks over the air.
Yeah, but you need to factor in the distance to the transmitter. Going to add at least a few microseconds to your time accuracy!
Latency is accounted for in the sync process
Sync process? The other comment was talking about the old receivers for the atomic clocks on SW/MW frequencies. It was a one way thing.
Now in theory if a receiver also had GPS they could account for the distance. But, then they'd get far more accurate time from the GPS receiver so..
The watches/clocks they are talking about listened to WWV, a set of radio stations transmitting from Fort Collins, Colorado. The system long predates the Network Time Protocol you're referring to. Radio controlled clocks/watches had no means for accounting for latency.
Ahh OK my bad. I've only worked with NTP for a long time and wasn't aware of the earlier stuff.
If you're interested in prehistory, listen to this for a couple minutes.