That's a succinct way to put it. Does anybody have any suggestions for following up on this line of thinking? I wonder what other, maybe technical scenarios, where this might also be true?
It's better for an error message to explain what the end user likely needs to know, rather than you heroically debugging it for them.