this post was submitted on 16 Aug 2024
789 points (91.7% liked)

Memes

45670 readers
2125 users here now

Rules:

  1. Be civil and nice.
  2. 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
[–] Incandemon@lemmy.ca 11 points 3 months ago (1 children)

To be fair, I did have a watch that automatically synced itself to the us naval observatories atomic clocks over the air.

[–] r00ty@kbin.life 4 points 3 months ago (1 children)

Yeah, but you need to factor in the distance to the transmitter. Going to add at least a few microseconds to your time accuracy!

[–] Unforeseen@sh.itjust.works 8 points 3 months ago (2 children)

Latency is accounted for in the sync process

[–] r00ty@kbin.life 4 points 3 months ago

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..

[–] Rivalarrival@lemmy.today 2 points 3 months ago (1 children)

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.

[–] Unforeseen@sh.itjust.works 1 points 3 months ago (1 children)

Ahh OK my bad. I've only worked with NTP for a long time and wasn't aware of the earlier stuff.

[–] Rivalarrival@lemmy.today 1 points 3 months ago

If you're interested in prehistory, listen to this for a couple minutes.