Reader-added tags include of "Zero day", "Y2K bug", and "There's always someone saving the Earth somewhere."

The Y2K bug actually did affect a few (US government?) computers, but not in the way which had been predicted. For a few minutes, those few computers thought the date was January 1, 19100.

Obviously that bug had been fixed in short order.

Now we just have to deal with the 2038 problem. Yes, it's 18 years away, but so many companies are bad at keeping hardware/software up to date. I wouldn't be surprised if a significant number of 32-bit *nix machines are still prevalent then.

The one Y2K error that I personally witnessed was on a video game site that, on 1/1/2000, instead listed the date as December 32, 1999.

I've long since forgotten which, or how long it took them to get it fixed.

EDIT: Wrong month.

Personally I have been looking forward to an 128-bit system for a looong time.

Incidentally, whilst looking that up, discovered the South Korean government is following the example of their brothers to the North [ Red Star ! ] and switching over to Linux, which is good; and more importantly found a new browser [ from Korea ] which works on Linux as well as other systems. Naver Whale.

https://whale.naver.com/en/

Probably won't drag me from Pale Moon, but one can never have too many browsers, particularly in the current browser drought

.

Certainly based on the inferior Chromium model, like 99% of browsers; but still...

Also they are poets even when misspelling:

Outdated enviornment, reckless security risks and,
unfriendly usabilty. Every user has to deal with these inconvenience
because of the terms of 'familarity'.
Our agony started with this problem.

Fixed a couple Y2K bugs myself... all before the actual day. Got stuck babysitting the servers on News Years Eve because I had just started at the company a few months before. Spotted one in the wild after, a "19100" on webcomic website.

According to Mizuki-san's Twitter, he had some problems that took up his normal drawing time, so there will be no strip for July 25 (US time). Presumably, this has nothing to do with the Y2K bug.