for those who downvoted: its pretty dangerous to take something that is traditionally done by humans or in an analog fashion and do it digitally when you are wrong around 50% of the time because people tend to trust technical things that look "safe enough." i understand the tech will get better, but i think its pretty bad to have attributes like "smiling?" and "male/female" even present in the API at all if i can flip a coin blindly and have roughly the same outcome.
of course its complicated, technically impressive regardless. but when a consumer sees "facial recognition technology" from the tech community they aren't about to question it. all im saying is if you are going to offer that kind of analysis, it should be right before people can start using it in their apps via an API and end consumers start depending on the data. if it's not accurate, or not a big enough a deal to care about, it shouldn't be in the API.
here come more down votes...sigh
it's a minor thing, with this example, i know, but how long before the precision of our digital measurement ends up hurting us because the layman doesn't understand its inaccuracy?
edit: this isn't a critique of face.com, but those who may end up using it. face.com = awesome tech, very cool.