Email or username:

Password:

Forgot your password?
Daniel Keys Moran

After 2000, *lots* of people sneered that the Y2K bug had been a big nothing, massively overhyped.

They were idiots. If the vast amount of Y2K remediation that took place hadn't, planes might well have fallen from the sky, nuclear power plants might well have melted down. I worked on two projects myself to fix bad 2 digit dates.

We get to the other side of the current Nazi infestation, the same idiots are going to say, "See, you were just hysterical."

66 comments
Daniel Keys Moran

That's the payoff for successfully winning this war, having to ignore the chorus of weak liberals and complicit conservatives, afterward. It's a small price, surely. But don't forget what it feels like, today, if we're lucky enough to head off fascism again. It was the complacent chowderheads and incipient Nazis who put us through this in the first place.

unlucio ๐ŸŒ :mastodon:

@fatsam empathy is not a weakness.
The only real weakness is ignorance, which conservatives, bigots, and libertarians have lots.

random thoughts

@fatsam
This is a great marker for idiocy. I frequently use it to judge people quickly.

Bรธ!rge

@fatsam @rysiek "we don't need vaccines" "we should drink unpasteurized milk and raw water"

Michaล‚ "rysiek" Woลบniak ยท ๐Ÿ‡บ๐Ÿ‡ฆ

@forteller @fatsam yeah. I really wish some people could just Find Outโ„ข on their own, without causing problems for the general population.

Rae Patterson

@rysiek @forteller @fatsam

Yes, it will be bad for the rest of us if some idiot drinks unpasteurized milk with the nasty new bird flu virus in it while also having a case of the regular flu, and becomes the latest one to rediscover influenza's ability to recombine.

Toadofsky

@fatsam Which planes and reactors were at risk? I understand that software which involves calendars and dates and financial records could be at risk, but I didn't think navigation systems or safety systems scheduled their meltdowns.

Daniel Keys Moran

@toadofsky most commercial flights were cancelled on New Year's Eve 1999. They were more worried about flight control than the individual planes, but there was patching done to quite a lot of individual subsystems in planes, as I recall.

Give me a minute on the nuclear power plants. I know there was at least one problem due just to testing.

Leeloo

@fatsam @toadofsky
That reads like the problem was someone messed up Y2k testing, rather than an actual Y2k bug.

Professor Emeritus Blake Y Rat

@leeloo @fatsam @toadofsky Other than the journalist's weird use of the word "antiquated" to describe analog indicators, it doesn't at any point demonstrate that the analog indicators are inferior to the computerized. (And why would they be? Nuclear reactors existed, safely, before computers were available for them, like in 1950s submarines)

I get the urge to push back on "Y2K was no problem!" but there's some over-correction going on here. This is just as wrong, but in the other direction.

cholling

@leeloo @fatsam @toadofsky True, but if the problem could be caused by an improperly set clock, it's not a stretch to think it could have been caused by a date overflow, too.

Adora (She/Her) :flag_transgender:

@toadofsky @fatsam systems use dates/times to monitor changes.

like "too much radiation leak" might be "X rads in Y time"

date/time failures could bring down key monitoring systems easily (I didn't work on Y2K, but I do make monitoring systems)

Zimmie

@toadofsky @fatsam The Boeing 787 has had quite a few time-related problems.

In mid-2015, the FAA reported the generator control units (GCUs) would all simultaneously hang after about 248 days of uptime, causing a total outage of AC power to the aircraft. The workaround was to reboot all of the GCUs after no more than 120 days up. arstechnica.com/information-te

Then in late 2016, they reported all three flight control computers could hang after 22 days up, leading to loss of flight control until they were rebooted. The workaround was to reboot them every week. seattletimes.com/business/boei

In early 2020, there was another problem which could result in the control network crashing or in weeks-stale data from a wide variety of plane systems being shown to the pilots as if it were current. Again, the workaround was to reboot the whole plane every three weeks. theregister.com/2020/04/02/boe

While these are all likely to be accumulators which overflowed, they all mean Boeing software is not developed particularly rigorously. I could definitely see a timestamp which the plane thinks is invalid causing flight control or engine control to go unresponsive. Particularly things tracked by rateโ€”when the timestamp overflows, the rate will be wildly nonsensical until the full rate window is past the overflow.

@toadofsky @fatsam The Boeing 787 has had quite a few time-related problems.

In mid-2015, the FAA reported the generator control units (GCUs) would all simultaneously hang after about 248 days of uptime, causing a total outage of AC power to the aircraft. The workaround was to reboot all of the GCUs after no more than 120 days up. arstechnica.com/information-te

Fear and Tooting in Las Vegas

@fatsam I mean, we did it with COVID tooโ€ฆ..

โ€œAll that time masking and it was for nothing.โ€

Resolviendo la incรณgnita

@fatsam That's why the rocket to the Sun was critical to its success.

decapitae

@fatsam Until it affects them, they don't believe. Same.with climate change. Aerosol pollution has been cooling the planet for a while, to the detriment of CO2 buildup. With aerosol pollution waning, thins are really taking off now. The yearly forest fires are probably mitigation techniques by corporate to slow the warming with light filtering global smoke clouds to extend sales figures. ๐Ÿ˜“
When the permafrost liquifies, even the smoke won't help anymore. Then its off to the races!

HeinousTugboat

@fatsam Reminds me of the hole in the ozone layer. People love asking "whatever happened to that?" And the answer is that we actually took action and fixed it.

Longplay Games :pc_color: ๐ŸŽฎ

@fatsam I managed the y2k lab for a major healthcare company, and we fixed *so many* showstopper bugs.
OS bugs, storage bugs, network bugs, and something like 2m lines of code fixes (and tons of the general tidying while fixing showstoppers).
Plus so much infrastructure spending had to be done that it basically powered the 2000s tech economy.
We had to replace millions in hardware and infrastructure that otherwise would have be left alone.

Longplay Games :pc_color: ๐ŸŽฎ

@fatsam To expand that to the current issues, it will likewise require enormous efforts to stave off the giant piles of imminent disasters, and if we succeed by some combination of Herculean effort and luck, it'll be minimized just like the CFC impact on the ozone layer.

That's the price our culture pays for success, we are an anti intellectual society.

Jeff Shaffer CBET, ret

@Longplay_Games
I was working in a hospital and spent months making sure that the date change wouldnโ€™t adversely affect patient care, had to intervene on multiple devices so that care was not compromised. Even though we thoroughly tested and remediated every device in our inventory, at midnight on 12/31/1999 I still was on duty at the hospital โ€œjust in caseโ€ and had to miss the celebrations. Was pleased that our work was successful, but it was both a tense and boring night!
@fatsam

Longplay Games :pc_color: ๐ŸŽฎ

@CivilityFan @fatsam Hah! Same, we had a huge party on the actual millenium though. The company even rented a boat.

I have very little respect for people who refuse to acknowledge the effort put forth to prevent disasters.

zetabeta

@fatsam
unix time may have 32bit implementation, so this could happen again, maybe in year 2038. good news is that t64 transition is going on in various systems.

leap seconds are problematic as well. scientific community has decided to abolish leap seconds, but it takes time.

Leeloo

@fatsam
That is a bad example, because y2k WAS massively overhyped.

Everything with integrated circuits was supposed to stop working. Computers, VCRs even the timers people use for their christmas decorations.

Pretty much none of that got updates, and yet the calendar changed to 2000 with people watching their VCR happily continue flashing 12:00.

My Commodore 64 has two of the affected chips with a two digit date, and last I checked it still works.

And the timers for christmas decorations are even worse, they run out of digits every 24 hours. The more expensive ones after 7*24 hours.

Yes, a lot of work was done, but the other 90% really WAS hype. And that stuff was way more visible than mainframes and cobol programs.

@fatsam
That is a bad example, because y2k WAS massively overhyped.

Everything with integrated circuits was supposed to stop working. Computers, VCRs even the timers people use for their christmas decorations.

Pretty much none of that got updates, and yet the calendar changed to 2000 with people watching their VCR happily continue flashing 12:00.

argv minus one

@leeloo

Yeah, consumer electronics were little affected. By the time microcomputers became common in the 1980s, it was already well known that a two-digit year wasn't going to suffice for long, so for the most part, they were Y2K compliant from the start.

But the machines keeping track of people's bank balances or the status of a nuclear power plant were much older, and programmed at a time when even a single byte of memory was scarce and valuable.

@fatsam

Leeloo

@argv_minus_one @fatsam
Incorrect, we had 486 PCs that didn't handle the rollover, that's much later than 1980.

But they didn't break, they just showed the wrong date until set manually. Just like the C64 I mentioned - the C64 had no battery, so the date would start at zero every time you turned the computer on, and nobody bothered setting the clock in the first place.

Same with the VCRs, the flashing 12:00 indicated that people didn't bother setting the clock.

Financial software needs to know the date for things like calculating interest, but most consumer stuff simply didn't care.

@argv_minus_one @fatsam
Incorrect, we had 486 PCs that didn't handle the rollover, that's much later than 1980.

But they didn't break, they just showed the wrong date until set manually. Just like the C64 I mentioned - the C64 had no battery, so the date would start at zero every time you turned the computer on, and nobody bothered setting the clock in the first place.

argv minus one

@leeloo

I'm surprised you had a 486 PC without a battery-backed hardware real-time clock. I was under the impression they all did. Mine did. It knew quite well what time it is when powered on (unless the battery died).

Indeed, a lot of 486 motherboards today are inoperable because the battery leaked and its corrosive electrolyte has damaged the board.

The original IBM PC didn't have a battery-backed RTC, though. That one did require you to type in the current time at power on.

1/

@fatsam

argv minus one

@leeloo

Anyway, some RTCs had a century register and some didn't. wiki.osdev.org/CMOS#Century_Re

Some RTCs with a century register suffered from a bug where it wouldn't actually be incremented. dell.com/community/en/conversa ๐Ÿคฆโ€โ™‚๏ธ

Not sure about my 486. It was powered on and running Linux when the century rolled over. If the RTC did have an incrementation bug, it would've been corrected automatically; resetting the RTC was part of the shutdown sequence.

2/end

@fatsam

@leeloo

Anyway, some RTCs had a century register and some didn't. wiki.osdev.org/CMOS#Century_Re

Some RTCs with a century register suffered from a bug where it wouldn't actually be incremented. dell.com/community/en/conversa ๐Ÿคฆโ€โ™‚๏ธ

Daniel Keys Moran

@argv_minus_one @leeloo I owned an original IBM PC. You could, and I did, buy an expansion board with more RAM and a battery-backed clock on it, though. (Serial port as well, I vaguely recall.)

Leeloo

@argv_minus_one @fatsam
I've reworded that - it was the Commodore 64 that didn't have a battery backed clock. Sorry, that could be read both ways, bad wording on my part.

Jeff Shaffer CBET, ret

@leeloo
Two issues I remember being resolved at the hospital I was working at involved remediation, one was a machine in nuclear medicine that would have shut down, delaying access and treatment to patients the next day (we just changed the date to 10 years earlier iirc) and the other was the date stamp on the ICUโ€™s central station monitor, which printed time on the ECG recorder, used for diagnostic and legal documentation. In that case, the vendor provided a patch we installed in the software.
@fatsam

@leeloo
Two issues I remember being resolved at the hospital I was working at involved remediation, one was a machine in nuclear medicine that would have shut down, delaying access and treatment to patients the next day (we just changed the date to 10 years earlier iirc) and the other was the date stamp on the ICUโ€™s central station monitor, which printed time on the ECG recorder, used for diagnostic and legal documentation. In that case, the vendor provided a patch we installed in the software.

Lion abt not making pride puns

@fatsam the good news is we won't get this one for catastrophic climate change, because we won't avert it

enoch_exe_inc

@fatsam In about fourteen yearsโ€™ time, history might well repeat for the Year 2038 problem, which is much more serious as itโ€™s literally the end times for systems that still use 32-bit Unix time.

enoch_exe_inc

@fatsam If something catastrophic occurs, the rabble will clamour that itโ€™s the end times. But if nothing particularly bad happens, then theyโ€™ll claim itโ€™s a hoax. Computer programming, when done correctly, is a thankless job simultaneously over- and under-appreciated by all of society that expects computers to be magical solutions to all their problems.

Mary Austin

@fatsam I was just thinking about this the other day: all cults end, and when this cult ends everybody who chose to be a member will be blaming everyone but themselves. They'll blame Fox News like the January 6 defendants are already doing, then keep watching Fox News because it will be telling them nothing really bad happened. Which Fox is already also doing with January 6.

And the leftists who both sides Nazism will still be spouting their nonsense.

Mary Austin

@fatsam
The original Nazi supporters all said after the war that they didn't support Hitler. These people will all have massive digital documentation of their support for Mango Mussolini and they will still deny everything. Again, it's already happening. Look at people like JD Vance, Nikki Haley, and Lindsey Graham when they are confronted with their old tweets condemning Trump and/or praising Joe Biden. Facts don't matter to these people now, and never will.

Steve Hersey

@fatsam
I long for that day.

And yes, Y2K was a catastrophe averted by lots of effort that went largely unnoticed precisely because it WORKED.

Helge Rausch

@fatsam I like the word "remediation" in the context of dealing with nazis! As I just learned, it can mean special-needs education, but it could also be read as an euphemism for more drastic measures.

Babs E. Blue

@fatsam getting to other side is a big IF rt now, sadly. But yr point is so true. Pls read #GregOlear 's new book...Rough Beast...he lays out in short concise terms how the U.S. will be a completely changed place by July 2025 if Trump gets back in power. It's written for Repubs & Indep who might be willing to see facts & hv them register - like NY jury which had 1 man who only got his news frm Truth Social.Fellow fascism fighters - pass it on-it $14 on Amazon & we nd to get it in ppl's hands!

j5v

@fatsam I managed Y2K internally for a tech/manufacturing company.

There was no thanks, because I did it well, and we didn't see the alternative history where it affected critical systems.

argv minus one

@fatsam

They already are. Trump tried to have the Affordable Care Act repealed during his first (and hopefully only) presidential term, which would have killed me, and people now tell me I was and still am overreacting. WTF! I'm lucky to still be alive right now!

Daniel Keys Moran

@argv_minus_one you and me both. I am diabetic, and on ACA insurance.

SamuelJohnson

@fatsam If you need detailed evidence that the Y2K bug was real and had real consequences. ๐Ÿ‘‡

Most potentially adverse consequences were averted by the expenditure of trillions of $ over many years in advance of the year 2000, and in some cases in the nick of time.

gresham.ac.uk/lectures-and-eve

Mister Moo ๐Ÿฎ

@fatsam If the Donner Party hadn't taken the Hastings shortcut, many of the 90+ members would've spent the rest of their lives wondering if they could've gotten to the west coast even more quickly.

John Faithfull ๐ŸŒ๐Ÿ‡ช๐Ÿ‡บ๐Ÿด๓ ง๓ ข๓ ณ๓ ฃ๓ ด๓ ฟ๐ŸงกโœŠ๐ŸปโœŠ๐Ÿฟ

@fatsam ๐Ÿ’ฏ this. I was departmental systems manager at the time. We did a huge amount of careful checking and fixing, and found a lot of things that would have failed if not sorted. Such careful, informed foresight seems completely unimaginable today. ๐Ÿ˜ž Or indeed even after Jan 2000 when the news media take was there had been nothing to worry about. ๐Ÿคฌ๐Ÿ˜ญ

Daniel Keys Moran

@FaithfullJohn I've got one trying to argue with me in this thread. Hadn't expected to run into it on Masto, to be honest.

Agnes

@FaithfullJohn @fatsam โ€œY2K wasnโ€™t that big of a dealโ€ is the vague impression I had until I took my first and only programming class in university, due to the fact that I was 9 years old at the time (and no adults around me worked in tech, even though I was in the SF Bay Area).

So itโ€™s great to see these counter-to-the-news-media personal stories on here, and at the same time, I can see how many people outside the tech bubble still might not be aware of the magnitude of it all, decades later.

John Faithfull ๐ŸŒ๐Ÿ‡ช๐Ÿ‡บ๐Ÿด๓ ง๓ ข๓ ณ๓ ฃ๓ ด๓ ฟ๐ŸงกโœŠ๐ŸปโœŠ๐Ÿฟ

@agnes @fatsam the really sad thing is that it shows careful prevention works superbly. But the message that got amplified was that nothing happened, so precautions are a waste of time, and we never need to worry about anything ever again ๐Ÿ˜ญ

Agnes

@FaithfullJohn Iโ€™m so very sorry that people didnโ€™t appreciate all of your hard work! ๐Ÿ˜ญ But I, for one, appreciate everything you and other tech industry veterans did so the world didnโ€™t crash and burn before I even got to 5th grade!

But there are lots of people who care about preventative work, and we will try our best to take your stories and pass them on, so please keep telling them! ๐Ÿ™

bytebro

@fatsam I spent several years in the late 90s sorting out y2k shite. The work that people like me and all those others that did similar got done stopped it being a really big problem.

Crimea River

@fatsam โ€œplanes would have fallenโ€ is an exaggeration. It was likely that ATC systems would have crashed, so planes would have had to divert to the nearest airport. If that was expected to happen, none would have taken off.

I agree with your wider point though.

Daniel Keys Moran

@bernardlyons if you're going to put quote marks around something responding to me, at least use my actual text. Might and would are not the same.

Most commercial flights were grounded on New Year's Eve 1999. I'll leave the rest to people who worked on those systems.

ArtBear on Catodon :catodon:

@fatsam
So much this.๐Ÿ‘†
Well we deccelerated the car to a stop avoiding a fatal accident, so clearly brakes are superfluous wokism & can be removed, because that accident didn't happen.....

Timo

@fatsam How many people recall the feelings/vibes from the Bush/Cheney years? That was clearly a nascent fascist time when people were attacked for speaking out against the Bush family wars.

aetios
@fatsam it comes back regularly that y2k was overblown. Until i read accounts of work by people in the industry I also thought it wasn't a big deal. The irony of actually fixing a problem before it's acute is that it seems like it was all for naught
Angry Sun
@fatsam The Y2K mitigations were done quietly behind the scenes, that's why people thought nothing happened. Do you figure that beating fascism will happen quietly
Jacqueline Jannotta

@fatsam same with pandemic measures and vaccines. Imagine where weโ€™d be if none of that happened.

Raqbit

@fatsam Recently I found this Y2.1K bug in the datetime encoding code of a smart home product/ecosystem. I wonder how many instances of this are present out there in the wild.

Go Up