• r00ty@kbin.life
    link
    fedilink
    arrow-up
    7
    arrow-down
    2
    ·
    4 months ago

    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

      • r00ty@kbin.life
        link
        fedilink
        arrow-up
        5
        arrow-down
        1
        ·
        4 months ago

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

          • r00ty@kbin.life
            link
            fedilink
            arrow-up
            5
            arrow-down
            1
            ·
            4 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
            link
            fedilink
            English
            arrow-up
            2
            ·
            4 months ago

            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
              link
              fedilink
              arrow-up
              1
              ·
              4 months ago

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