Conversation

Notices

1. Embed this notice
   Jon Rowe (jonrowe@fosstodon.org)'s status on Tuesday, 02-Jan-2024 07:03:40 JST Jon Rowe

   • Thomas 🔭🕹️

   @thomasfuchs its the same dangerous revision as “the hole in the ozone layer was never a problem”, its sadly being used as propaganda for “there was fuss over x but nothing happened, so fuss over y is unnecessary" where y is something the propagandists don't want to prevent, like ai, or climate change

   • Embed this notice
     ADisorderlyFashion (adisorderlyfashion@mas.to)'s status on Tuesday, 02-Jan-2024 07:10:38 JST ADisorderlyFashion

     • Thomas 🔭🕹️

     @thomasfuchs People think I'm overreacting when I say that y2k38 (I personally prefer the term epochalypse) is going to break a some hardware everybody forgot they depend on for everything and the first few months of that year are going to suck. This confirms my fears.

   • Embed this notice
     Ana Hevesi (anthrocypher@hachyderm.io)'s status on Tuesday, 02-Jan-2024 07:17:22 JST Ana Hevesi

     • Thomas 🔭🕹️

     @thomasfuchs any and all stories you ever want to tell about this experience I am HERE for

   • Embed this notice
     ChookMother 🇦🇺🦘 (anne_twain@theblower.au)'s status on Tuesday, 02-Jan-2024 07:51:16 JST ChookMother 🇦🇺🦘

     • Thomas 🔭🕹️

     @thomasfuchs Amusing that some younger peeps will argue with you about something that you experienced first hand

   • Embed this notice
     J.P. Wing (machias@hachyderm.io)'s status on Tuesday, 02-Jan-2024 08:00:30 JST J.P. Wing

     • Thomas 🔭🕹️

     @thomasfuchs I spent the last few months showing folks they could run their point of sale systems as if it was 1971 going to 1972 until they had a chance to upgrade after the first of the year

   • Embed this notice
     David Megginson (david_megginson@mstdn.ca)'s status on Tuesday, 02-Jan-2024 09:56:19 JST David Megginson

     • Thomas 🔭🕹️

     @thomasfuchs I worked for 3 years on #Y2K stuff

     Here's the thing: many dates aren't point-in-time but past/future. We should have seen the left half of a massive bell curve of failures for 10–20 years before the year 2000 (and before we started fixing it seriously), e.g. mortgages being flagged as 80 years late for renewal, reactors shutting down because their maintenance was 95 years late, etc.

     We didn't see that. The Y2K bug wasn't fake, but it was massively overhyped.

   • Embed this notice
     dontony (dontony@hachyderm.io)'s status on Tuesday, 02-Jan-2024 09:59:03 JST dontony

     • Thomas 🔭🕹️

     @thomasfuchs just like how we fixed the ozone layer

   • Embed this notice
     Ryan Baumann (ryanfb@digipres.club)'s status on Tuesday, 02-Jan-2024 10:18:37 JST Ryan Baumann

     • Thomas 🔭🕹️

     @thomasfuchs when I was 15, I fixed a Y2K bug in a compiled System/36 billing system with no source available

   • Embed this notice
     Tom Larrow (tomlarrow@vis.social)'s status on Tuesday, 02-Jan-2024 10:32:06 JST Tom Larrow

     • Thomas 🔭🕹️

     @thomasfuchs I spent 98-99 testing, certifying and applying patches to television production equipment

     It took a patch to make the switcher that blew up Alderaan Y2K compliant

   • Embed this notice
     dcozy (dcozy@zirk.us)'s status on Tuesday, 02-Jan-2024 10:43:15 JST dcozy

     • Thomas 🔭🕹️

     @thomasfuchs Well, I guess you did a good job, because as far as I know, nothing anywhere "completely and utterly fail[ed]".

   • Embed this notice
     GuySoft (guysoft@hayu.sh)'s status on Tuesday, 02-Jan-2024 17:47:52 JST GuySoft

     • Thomas 🔭🕹️
     @thomasfuchs
     Also this might be less expected https://en.wikipedia.org/wiki/Year_2038_problem
   • Embed this notice
     lolcat (lolcat@digipres.club)'s status on Wednesday, 03-Jan-2024 00:51:24 JST lolcat

     • Thomas 🔭🕹️

     @thomasfuchs
     First half of 1997. Major US wireless carrier. Found and fixed thousands of Y2K bugs. Also learned that the world of difital commerce is held together mostly by luck. Good grief, was that code bad. So, so bad.

   • Embed this notice
     TheDude (thedude@cville.online)'s status on Wednesday, 03-Jan-2024 01:26:02 JST TheDude

     • Thomas 🔭🕹️

     @thomasfuchs I worked at a large company that had this Y2K policy: if code you wrote failed at Y2K, no matter how trivial, you were fired.

   • Embed this notice
     unicorndeburgh (unicorndeburgh@hachyderm.io)'s status on Friday, 26-Jan-2024 08:43:36 JST unicorndeburgh

     • Thomas 🔭🕹️

     @thomasfuchs Yup. Portland couldn't send out water bills to customers for months because their old system couldn't handle 4-digit years.

     We all did SO MUCH work, and so much equipment was replaced.