You can give your users an option to provide you with these details but guessing/requiring is not a good practice.
On a side note, it's interesting that the most common gender neutral title is Dr.
31–40 of 55 posts
You can give your users an option to provide you with these details but guessing/requiring is not a good practice.
On a side note, it's interesting that the most common gender neutral title is Dr.
I agree with many of the concerns and limitations brought up here, most notably the fluid, non-binary nature of gender. That said, thoughtful application of probabilistic guesses about gender can add value in certain situations. For instance: http://source.mozillaopennews.org/en-US/learning/freeing-plu...
It got interesting when occasions didn't warrant possessives ("What should I get my boyfriend for Christmas"), and when language factors were considered ("What should I get mi abuelo for su cumpleanos"). We decided to try and crowd source it, which worked ok: essentially we left the occasion empty, and if the person wanted to attach the gender-based possessive to it, they could. Otherwise, we would guess with what information we had. We figured, over time, we could actually create a service where we could sell that information (GaaS: Grammar as a service?).
Turns out, people just wanted to be able to write their own titles, and we quickly trashed the idea in the early phases.
As a man named Tracy I would just throw out a caution to anyone thinking of using this. At this point in my life I don't really care about people calling Ms. Tracy Platt. But what it does do is immediately signal that I don't really need to pay attention. Fake familiarity doesn't usually work too well. As a side note I would like to mention that having a girl's name does have some benefits. For example my wife can ha…
Me and my significant other frequently impersonate each other when dealing with banks and hospitals over the phone (we're a gay couple). It honestly never occurred to me that straight folks can't get away with this. How unfortunate; it's quite a time saver!
Really though, geek PC hilarity aside... with so many collisions and uncertainties, this just isn't a practical approach.
Gender identity is actually a quite tricky topic and should be approached carefully. I would discourage anyone from trying to use this library, the real world doesn't fit neatly in your multiple-choice view of gender. For more information, please watch this great talk: http://vimeo.com/61172068 .
Shouldn't this be called "Gender Machine", they get it right on the project description but not on the project name, weird.
Without knowing what data it's been trained on it's of questionable use. What maybe a 18 year old american girls name may be a 60 year old german mans name. The gender of a name can vary heavily by culture and time-period, it would make much more sense for the api to return the data in the form of ranked probabilities. As an aside it's worth noting that as this library is GPL3 it means you can't use this code in any…
> Without knowing what data it's been trained on it's of questionable use. Literally the very first line of the README has a link to the source data. It contains name frequency data for a number of countries and the README clearly indicates you can provide a country of origin when doing lookups. > As an aside it's worth noting that as this library is GPL3 it means you can't use this code in any non-GPL product. The s…