Thanks, njc. I started reading it but had to spend the rest of the day dealing with other people's f-ups. I'll finish the rest of the article later this week. If other people only did their jobs the way they're supposed to, we'd all have a lot more free time, and companies could shrink their call centers.
For example, a few months ago, I tried logging into the Alberta government's portal, which allows us mortals to perform functions without having to deal with chronically understaffed call centers. Well, for some reason, my new computer (HP Win11 Chrome) kept getting an error 429 when I tried to log in, reset my password, recover my username, etc. Useful error message if ever I saw one. So, I called the call center (non-IT folks) who asked a few questions, including whether or not I have another computer. Turns out I do - a Chromebook. So I trundled downstairs to try it, and it worked. At that point, the tech guru at the call center concluded the problem lay with my PC and I'd have to call the manufacturer. When I pointed out that my HP works perfectly with thousands of websites I'd visited since buying it, he insisted there was nothing that could be done at their end. When I asked to speak with someone in IT to do more troubleshooting, he said there was no one he could transfer me to, and repeated that I'd have to speak to the manufacturer. Can you imagine the call with HP Support: My HP doesn't work with Alberta.ca's login page, although it works everywhere else, but the highly technical call center folks insisted it must be a hardware problem. 
Fortunately, there is another way to contact support, which is through email. So, I sent them an email and made my case, including the fact that just because their software works with some PCs, doesn't mean the problem isn't on their side. I eventually got an email back (an electronic form letter), which explained some possible causes of error 429, and things to try, up to and including reinstalling Windows. Can you imagine? I went so far as the step to reinstall my browser but then stopped. I emailed back that I had tried everything (a fib, I know) and asked what else they suggest. That was the last I heard from them. About two weeks later, I tried logging in again, and lo and behold, it worked. I guess whatever hardware problem was causing the error must have self-corrected. :-)
This is the kind of crap I was dealing with all day. :-(
Dirk