Depictor: stop claiming so many digits of precision for clock skew
In https://consensus-health.torproject.org/#authorityclocks we state clock skew numbers like "-0.386114 seconds".
There's no way that 114 part is at all accurate, since this figure is influence by (for example) network latency, Tor processing latency, etc.
We list only 1 or 2 or 3 digits after the decimal point. I'm thinking two digits would be a nice balance.
Motivated by the discussion on tor-relays@: https://lists.torproject.org/pipermail/tor-relays/2020-April/018372.html