Entry № 041-8 / V-415 · 0:00 synced

Y2K Never Ended!

Techquickie@techquickie284.4K viewsJun 18, 20215:04
Source
YT
Views
284.4K
Subscribers
4.3M
Critic
?
Audience
?

0 up · 0 down · 0 ratings

Promos

Check out the Hammer Fidget Spinner Artizen Keycap from Drop at dro.ps It might not be the year 2000 anymore, but computers have still been causing date-related shenanigans... Leave a reply with your requests for future episodes, or tweet them here: twitter.com ►GET MERCH: lttstore.com ►SUPPORT US ON FLOATPLANE: floatplane.com ►LTX EXPO: ltxexpo.com AFFILIATES & REFERRALS --------------------------------------------------- ►Affiliates, Sponsors & Referrals: lmg.gg ►Private Internet Access VPN: lmg.gg ►MK Keyboards: lmg.gg ►Nerd or Die Stream Overlays: lmg.gg ►Official Game Store: nexus.gg ►Amazon Prime: lmg.gg ►Audible Free Trial: lmg.gg ►Our Gear on Amazon: geni.us FOLLOW US ELSEWHERE --------------------------------------------------- Twitter: twitter.com Facebook: @LinusTech Instagram: @linustech Twitch: twitch.tv FOLLOW OUR OTHER CHANNELS --------------------------------------------------- Linus Tech Tips: lmg.gg Mac Address: lmg.gg TechLinked: lmg.gg ShortCircuit: lmg.gg LMG Clips: lmg.gg Channel Super Fun: lmg.gg Carpool Critics: lmg.gg

Start
AI OverviewDefault language

Y2K Never Ended! digs into how the infamous Y2K scare was ultimately mitigated, while also exploring other date-related bugs that surfaced long after 2000. The video opens by recalling the widespread anxiety of the late 1990s, explaining how computer systems were believed to misinterpret dates, potentially causing cascading failures across industries. It then shifts to concrete historical episodes, such as a 2010 software bug in Germany that froze millions of bank cards and ATMs because the microchips could not recognize the year 2010. The presenter highlights the high cost of replacing the cards, the patch that resolved the immediate crisis, and the broader lesson that many problems were averted thanks to proactive fixes. The narrative continues with a 2019 GPS time rollover issue tied to a 1023 week counter, which briefly disrupted flights and location data for older devices, underscoring how even well-functioning systems can be tripped up by time calculations and counter limits. The video contrasts these incidents with the Unix 2038 problem, explaining why a 32-bit time counter would roll over and the complexities involved in upgrading entrenched software and embedded systems without unintended consequences. The closing segment projects a future risk around the year 10,000, pondering whether five-digit year representations will be needed and humorously imagining possible mechanisms to prevent missed astronomical calculations. Overall, the episode blends historical context, technical explanation, and light-hearted speculation to show that while 2000 was a predictable non-event, timekeeping bugs persist and will likely evolve in interesting ways.

Topics · technology · science_and_technology · history · computing

Questions answered

What caused the 2010 German bank card outage and how was it resolved?
The outage happened because the microchip in the cards could not recognize the year 2010. A software patch was issued to fix the issue, avoiding a costly replacement of the cards.
Why is 2038 a problem for Unix-like systems and is there a workaround?
The issue arises from a 32-bit time counter that will overflow in 2038. Upgrading to 64-bit time counters in Unix-like systems avoids the rollover, though implementing this change across many programs and devices can be complex.