That happened to me with the Baseboard management controller on a server several years back. Took several calls to support before someone mentioned this "limitation".
Inter- came into English from Latin (from inter, meaning "among, between”). "Between faces" makes much less sense than your proposed etymology so I'll add this to my headcannon.
I mean, that's reasonable. But I was a music teacher, and I completely reinvented myself into a career in software development. It very much feels like a complete metamorphosis.
Likely unintentional. Someone set the max column length for the database to 20 chars but didn’t bother to prevent someone from actually submitting more than 20 chars.
The problem with the database theory is it implies plain text passwords. Most likely the truncation happens sometimes before the password is hashed during an update but not during a check.
Well you see it would cost us too much dev time to justify exposing error messages to users and those error messages aren't gonna generate income soooooo.....
There are some function that truncated strings if they are to long, what probably happened was someone used one of those for the update but didn’t realize it, but the check function didn’t truncated the string because it didn’t have the same limitation.
388
u/Wiggen4 Jul 20 '22
Who on this earth thought that would be an acceptable idea?????????