this post was submitted on 06 Oct 2024

35 points (92.7% liked)

Watches

2375 readers

1 users here now

Welcome to /c/watches – A Hub for Watch Enthusiasts on Fediverse! ⌚

Whether you're a seasoned collector, a casual wearer, or just starting your horological journey, this is the place for you! Join us to:

🔹 Discuss – Share your latest watch acquisitions, ask for advice, or geek out over movements and designs. 🔹 Discover – Explore vintage classics, modern marvels, and upcoming releases from luxury to affordable brands. 🔹 Learn – Get insights on watchmaking, maintenance, modding, and industry trends. 🔹 Connect – Meet fellow enthusiasts, trade/sell watches (if allowed), and participate in events or meetups.

Rules: Be respectful, no spam, and keep discussions civil and watch-related.

founded 3 years ago

MODERATORS

Akimoto@lemmy.ml

roserose56@lemmy.ca

35

Fucking Time Propagation (lemm.ee)

submitted 9 months ago* (last edited 9 months ago) by pineapplelover@lemm.ee to c/watches@lemmy.ml

17 comments fedilink hide all child comments

Just bought the GWM 5610U-1C. It was a tough decision choosing between the DW5600 and this, ended up choosing this because the atomic time keeping is cool.

However, I'm a tad annoyed that the time doesn't perfectly match with time.gov and time.is since the atomic sync doesn't account for time propagation, so there's like a fraction of a second delay that's noticeable. Other than that, the watch is fantastic and has most features I would want. (I wish it had barometer and altimeter stuff, maybe even compass, and dive rated so I can press buttons underwater)

you are viewing a single comment's thread
view the rest of the comments

[–] Bach37strad@lemmy.world 2 points 9 months ago* (last edited 9 months ago) (1 children)

Delays in network infrastructure. While most signals going between large nodes/hubs will be fiber optic, there's quite a few old school copper connections between you and the time server that will slow things down. My ping to my closest node, with all my fiber and cat5e connections is still 20ms.

You're probably better off using a cellphone time than a desktop computer to a website, since the cell network accounts for the difference in time dilation between us and the satellites (Einsteinien relativity amitright?) supposedly well enough for network infrastructure to work.

You're also getting to "is the processor in the watch fast enough" territory. That's a bit beyond me though.

[–] pineapplelover@lemm.ee 1 points 9 months ago

The watch would be radio controlled so the delay wouldn't be determined by the network infrastructure but by the interference in the air. The watch's stopwatch can do split second 1/100 so surely it is precise enough. I'm leaning towards this being an issue of interference.