It’s time to leave the leap second in the past

What this post added

This post details Meta's support for an industry effort to eliminate future leap second introductions. It explains the technical challenges and risks associated with leap seconds, including system crashes, data corruption, and outages caused by unexpected time jumps or smearing implementations. The post describes Meta's current practice of 'smearing' leap seconds over 17 hours using quadratic algorithms and highlights the complexities of time synchronization across different GNSS constellations and NTP servers. It advocates for replacing leap seconds with technologies that provide a more stable and predictable time reference for digital applications.