timex

The reporting wrote, in his first paragraph: >Google doesn't provide timeX.google.com as a public service.

Never mind the lack of Timex / Sinclair or TI computers in that spreadsheet.

See Veblen Good; if nobody looks at your rolex it's just a heavy timex.

The Tao for me was: Timex Sinclair, Vic-20, C-128 and Amiga 500.

Nor can I, but I'm a Luddite with a cheap Timex and the smallest, dumbest off-contract phone I could find.

I am old enough to have lived through the Casio and Timex smart watches craziness.

Back when I was learning, I had Timex 2068 Basic and Z80.

I had an Atari 2600 and a TI-99/4A, another had a Timex Sinclair and Intellivision, another a ColecoVision (no computer), and 2 others had an Apple II (no consoles).

Clock: inserting leap second 23:59:60 UTC If ntpd gets notified of an impeding leap second via its peers (or the connected radio clock, GPS receiver,...) it will set (struct timex*)->status |= STA_INS via the timex syscall (which it also uses to steer/speed-up/slow-down the clock).

"Google doesn't provide timeX.google.com as a public service" seems pretty straight forward?

The issue is not that systemd is using NTP servers from a single corporate entity, it's that timeX.google.com are not meant to be public NTP servers: they do not provide UTC time they provide "Google time" and this difference will cause problems unless you intentionally want "Google time" and know what you're doing.

Timex's Ironman series performs its intended function well because the lap button is easy to locate without looking.

I literally thought it was a old, cheap Timex.

I'm not buying and discarding $20 Timex's every year.