Facebook's Name Policy Strikes Again, This Time at Native Americans
eff.org
eff.org
Edit - it appears the name check wasn't formalized into actual code, but rather policy.
Re: the culture/race/ethnicity terminology quagmire, the sister comment by dragonwriter explains it well.
Source: http://dst.dk/en/Statistik/emner/navne/navne-i-hele-befolkni...
I had a pretty strong emotional reaction to this policy. I can imagine it would be pretty distressing to run into this problem as e.g. a Native American or transgender person.
Change of policy over time turns what was possible in the past to "no longer acceptable" today.
Keep in mind that you have no right and no control over anything in the facebook world and you can explain every quirks.
I'm surprised no one's linked to the below posts already.
http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b...
http://infiniteundo.com/post/25326999628/falsehoods-programm...
> (#11) People’s names are all mapped in Unicode code points.
Well, not really sure how to fix that one!. Maybe one day postgres will be able to index a column of handwritten images, but until then I think I'll just stick with being 99% ok.
"Hey Facebook, I am SURE this Mark guy made up that last name. I am POSITIVE!"
The "real name" policy is entirely about raising the perceived value of their dataset.
They ban names like Laughing Critter, despite being real names, because they incorrectly believe that they are fake names.
They're not working with perfect information here. Their strategies have false positive and false negative rates, which they seemingly consider acceptable (hence the outrage. If you can make facebook reevaluate the cost of a false positive (by associating those false positives with outrage), then you may be able to influence facebooks behavior).
http://www.theonion.com/video/cias-facebook-program-dramatic...