A lot of people are making disparaging comments about the acccuracy of the site's time estimation with little or no explanation/data. All things considered (thr

A lot of people are making disparaging comments about the acccuracy of the site's time estimation with little or no explanation/data. All things considered (three samples to estimate clock deltas and network delay) the time estimation is fairly accurate. time.is reports my clock is: -0.004 seconds (±0.021 seconds). I have a stratum one time source on the local network (gps+pps) and my ntptime agrees with the time.is estimation: dfc@bushido:~$ ntptime ntp_gettime() returns code 0 (OK) time d3077752.4160a634 Sun, Mar 11 2012 15:11:14.255, (.255381196), maximum error 260579 us, estimated error 3294 us, TAI offset 34 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset -4842.630 us, frequency 8.446 ppm, interval 1 s, maximum error 260579 us, estimated error 3294 us, status 0x6001 (PLL,NANO,MODE), time constant 10, precision 0.001 us, tolerance 500 ppm, NB: this is my laptop. so powersaving, heat fluctuations are adding a decent amount of uncertainty from a metrological standpoint.