3 ms·
The problem is not a trust/surveillance issue. From the first comment: > We (Google) use this for systems outside of our datacenters that need to understand o
by sangnoir 11y ago
The problem is not a trust/surveillance issue.
From the first comment:
> We (Google) use this for systems outside of our datacenters that need to understand our concept of time.
> Google (famously(1)) runs a non standard concept of time, that works well if everything in your infrastructure knows and understands this and is designed to work with this. If you mix and match NTP servers within a machine you'll run into problems (since Google's timeservers are deliberately false ticking).
IIRC, Google handles leap-second changes by spreading it over a day (or two). This will not end well if you also use other NTP servers that do things differently
- 0fucks 11y agoYes I know that from a purely technical point it is not a trust issue but an issue with skewed time servers providing google-time instead of utc. My point is still that anyone who deliberately forces others to use google's services is a dangerous individual. System time is an identifier. I would never allow Google to control that. I take care never to use google for anything. This really upsets me. The thoughtlessness is beyond me.