This needs either external pressure on the people writing them or an independent solution. Reality is it's only independent solution. I'd suggest a hash or a h

This needs either external pressure on the people writing them or an independent solution. Reality is it's only independent solution. I'd suggest a hash or a heuristic hash or a 3rd party algorithm run on the error linked to a crowed sourced location the user can chose. So the 3rd party can say ignore this it's stupid. Something the original error message writer could never tell their boss. Or when the error was written their info was wrong, now it's this. Or they can say use root permissions on the code. Or undo this security patch. And just like Stack, people could explain why and why not. Teach around the error. Their conclusion "that the difficulty of reading error messages is comparable to reading source code" can't be solved at the error message writers level. Politically or even for the ultra high users who need the hard core message. Even by allowing the user to rule out the easy solutions it might give, they can turn their brain back to source code mode to tackle it.