I'm not sure about hyphens -- unusual punctuation is disallowed, and I recall seeing complaints about apostrophes causing trouble, but I don't remember whether hyphens are considered "ordinary" puctuation or not.
And all of this is stuff that -- even if we grant them the arguably racist "normal [American] looking names" constraint -- would be understandable in a high school student's first computer program, but shouldn't get a passing grade in a freshman college programming class, much less show up in a real-world professional large-scale system.
Not that Google is the only entity making such boneheaded name-format assumptions, mind you. (On the web, similar examples abound.) Just that after all their fuss about "real[-looking] names", I'm not willing to cut them any slack for getting real real-names wrong.
Especially when (AIUI) their data-entry form does let names like this in, and then they kick people off for using these names! The usual pattern is a company that means to allow correct names but gets the validation code wrong on the form.
Which is worse, not being able to enter your name in the first place, or being able to enter it correctly and then being kicked off with a "your name doesn't look right" notice days or weeks later?
Oh, no, I completely agree with you. That was just what occured to me.
Which is worse, not being able to enter your name in the first place, or being able to enter it correctly and then being kicked off with a "your name doesn't look right" notice days or weeks later?
Someone was auto-suspended for changing to their full legal name, which contained a hyphen on the first name. They then had to submit ID to prove it to Google, which is another rant entirely.
(no subject)
And all of this is stuff that -- even if we grant them the arguably racist "normal [American] looking names" constraint -- would be understandable in a high school student's first computer program, but shouldn't get a passing grade in a freshman college programming class, much less show up in a real-world professional large-scale system.
Not that Google is the only entity making such boneheaded name-format assumptions, mind you. (On the web, similar examples abound.) Just that after all their fuss about "real[-looking] names", I'm not willing to cut them any slack for getting real real-names wrong.
Especially when (AIUI) their data-entry form does let names like this in, and then they kick people off for using these names! The usual pattern is a company that means to allow correct names but gets the validation code wrong on the form.
Which is worse, not being able to enter your name in the first place, or being able to enter it correctly and then being kicked off with a "your name doesn't look right" notice days or weeks later?
(no subject)
Which is worse, not being able to enter your name in the first place, or
being able to enter it correctly and then being kicked off with a "your
name doesn't look right" notice days or weeks later?
A choice of suckitudes!
(no subject)