Re:Apple iCloud account and sign in outage affecting some us...
by proactivesvcs on Saturday December 26, 2020 @09:03PM
(#25548192)
A few weeks ago I scanned the Windows 10 BSOD QR code for the first time, out of curiosity. Since the BSODs no longer show any useful information other than the terse STOP description, I expected both that, the STOP code and the four parameters, perhaps also a link to that code's web page. Nope. Just a link to https://windows.com/stopcode
Re:Apple iCloud account and sign in outage affecting some us...
by colejohnson66 on Sunday December 27, 2020 @11:14AM
(#25551968)
The problem (I think) is that as soon as a detailed error message is given (or some error code), sites will pop up all over the place telling you to download their software to fix “error code 0x80000008” or whatever. It’s so annoying searching a Windows error code only to have 9/10 of the results be generic SEO spam for some garbage software that (1) doesn’t fix the problem and (2) costs $40+.
Re:Apple iCloud account and sign in outage affecting some us...
by ryukafalz on Saturday December 26, 2020 @04:33PM
(#25546610)
Here's a compromise: "Something went wrong, try again later. Click here to see more details."
I would like to see more details. Sometimes I won't be able to interpret them, often I will be able to, and I'd rather be able to see why something failed so I can fix it.
Since Microsoft went the UWP route, these nice error codes have been starting to vanish. Probably because when end users see an error they don't understand, their mind goes blank and their instinct is to click whatever button that makes the error go away, leading to confusion. A simple "try again later" will be a much more enjoyable experience for non-technical people than "Could not update your computer. The foobar failed to parse the widget tree (0xc0000005). Try again later."
When I did customer service, this trend had always irked me about Apple devices. I've had to tell a lot of people to contact Apple (which they never did of course, silently blaming us for their device not working) because all Apple's software said was "try again later".
And now it's spreading to other devices as well. Even if error codes are available, the error messages have been simplified and most error codes aren't documented. I wish there was some kind of generic standard shortcut or gesture that copied the stack trace of any fancy exception to your clipboard so people with technical know-how can actually solve the problem instead of getting told to "try to reboot my router" by a vague, generic help page when Netflix can't find a video stream that matches my video decoding hardware.