Issue with loading of the atomic clocktime

[AlphonseJr]

I got this message from a user, I was unable to reproduce on my side but that's kinda normal if it's a firewall issue :

"When the app says it's trying to figure out the atomic
clock time, it just spins and spins. I guess that my firewalls
are blocking something. Switching to cellular network, it works.

It appears that you're not using NTP to figure out the time
(you could use the strata to get VERY accurate timing -- more
accurate, I'd guess, than that of a person clicking the button
at "12" which is really +- a good half second).

Thus, I can't use it through my network."

Let me know if you want to be put in contact with him.

[MathieuNls]

"When the app says it's trying to figure out the atomic
clock time, it just spins and spins. I guess that my firewalls
are blocking something. Switching to cellular network, it works."

If he can login, he can be synced with the atomic clock. That's a known bug #23.

It appears that you're not using NTP to figure out the time
(you could use the strata to get VERY accurate timing -- more
accurate, I'd guess, than that of a person clicking the button
at "12" which is really +- a good half second).

From the about page : Toolwatch synchronizes your browser/app with the U. S. Naval Observatory's atomic clocks cluster which produces a weighted average of several commercial atomic frequency standards. It is dominated by six active hydrogen masers, there are also a number of commercial cesium beam-tube standards in the cluster. We also account for the networking time between you and Toolwatch' servers.
To put it simply, we do not use your computer clock but the most accurate atomic clock on earth to synchronize your timepieces.

The technology behind this is NTP. More precisely, we use the median of different Stratum 1 servers. Stratum 0 being the atomic clock itself.

Now, for the clicking part, yes, there is room for human error there. Won't be fixed until #1 .