Show HN: An API for gender classification
gender.hankstoever.com
gender.hankstoever.com
A better strategy all-round would to be ask yourself whether you need to know someone's gender. I can think of very few legitimate reasons to know and record a user's gender and many of them can be dealt with by simply asking them what they'd like to be referred as, perhaps in more than one scenario.
Turns out gender is great to include in a blocking keys to reduce number of comparisons. Extrapolating an inferred gender in the dataset without one was incredibly helpful.
A person using the name "Jack" is unlikely to be assumed to be a woman, even if that person selected "female" from a drop down somewhere. If the same person uses Jack/M and Cindy/F in different contexts, no fuzzy algorithm is going to resolve them as the same person (bar some other, stronger ID, such as a SSN).
EDIT: I initially used "William" as an example. Ironically, it turns out that name is only 57.6% male. Both Jack and Cindy are 90% male/female.
You have just used the numbers from the API as evidence of its own accuracy.
Developers have a horrible tendency to gather as much data on someone as possible, everything they're willing to give in fact, for the simple reason of "just in case we need it later". It's far, far better to gather as little as possible and build something that simply doesn't need to know specifics. If we build things that are ambiguous, unspecific for age, gender, race, nationality, etc then the world will be a better and more inclusive place. Paradoxical as it seems, more privacy actually leads to a more integrated society. That is universally a good thing (in my opinion, obv.).
Also this: http://www.cscyphers.com/blog/2012/06/28/falsehoods-programm...
"Sex" refers to the biological and physiological characteristics that define men and women.
"Gender" refers to the socially constructed roles, behaviours, activities, and attributes that a given society considers appropriate for men and women.
[1]:http://www.chw.org/display/PPF/DocID/22620/Nav/1/router.asp
http://en.wikipedia.org/wiki/Unisex_name has been mentioned elsewhere, but I've found it pretty useful.
Unlike a lot of people here, I don't think there is anything wrong with an API like this. It's true that it isn't culturally neutral, but there are times when any piece of information is useful.
if probability == "59.369936" {
probability = "?"
gender = "unknown"
}In the present case, the API is, unfortunately, incorrect.
Michael = 52%, Thomas = 62% (although Tom = 98%)
'Eric' (which often becomes Erica for females) scored a 10% higher chance of being male than 'John' did (Eric = 66.854585% while John = 57.399103%).
What's also surprising is the dramatic change the Anglicizing of the name brings: 'Erik' = 91.939346% while 'Eric' = 66.854585%