Started by Callum Reid (@callum_r) ·
the year 2038 problem
At 03:14:07 UTC on 19 January 2038, a signed 32-bit Unix timestamp overflows and wraps to 1901. Most modern systems moved to 64-bit time, but embedded stuff lives a long time.
4 sources · 21 min down the hole
How I got here
- Started with
- “year 2038 problem”
- Ended at
- Year 2000 problem
The Trail
- “year 2038 problem” (google.com)
- Year 2038 problem (en.wikipedia.org)
- Unix time (en.wikipedia.org)
- Year 2000 problem (en.wikipedia.org)
Keep going
- a second is 9,192,631,770 wiggles of a cesium atom · Dev Malhotra · 5 sources
- the theory that 297 years of the middle ages never happened · Yuki Tanabe · 6 sources
- a Roman hour wasn't always the same length · Jonas Becker · 5 sources
- leap seconds are being retired · Ilya Smirnov · 4 sources