|
|
|
|
|
by manfredo
2294 days ago
|
|
It's not a bad idea to conjecture about, but it's not very useful as far as implementations go. Brainstorming possible ways in which users might be offended by software and trying to mitigate said hypotheticals is not very productive. Furthermore, there are consequences of trying to avoid offending people. If this automated email wasn't sent, this blog author would suddenly gotten a roommate with no warning. Would that have been a better situation? A lot of these things cannot feasibly be thought of in advance, and the offense is often more due to ignorance of the automated nature of the system. E.g. at a coding summer camp people received passwords with two random words and two random numbers. Profanity was blacklisted as well as some number combinations (69, 88, maybe more). One class had someone take offense at the password "bloodyunhappy12" - thinking this was a derogatory reference to menstruation. Are we really going to try and think of every pair of words that might cause offense? Letting people pick their own passwords meant a lot of people had insecure passwords, so this random words + numbers was the best approach. Similarly an airline got in trouble for generating a confirmation code "H8GAYS": https://www.buzzfeednews.com/article/adriancarrasquillo/delt... |
|