Well, it's not really a verification method, it's the use of age estimation models in a computer vision sense. The problem with age estimation models is they are only better in statistically unreliable ways within controlled ethnic demographics. That word salad means that age recovery trained algorithms have a variance of accuracy that is difficult to reduce, and when successful is only successful on narrow classifications of ethnicity. Part of the issue is ethnicity carries meaningful changes in age representation. Asian, African and several other ethnicity show age later and significantly more subtle than others. Now add in the existence of large demographics of mixed ethnicity, and then add in the issue of the uncontrolled illumination age verification systems are expected to operate... and age verification computer vision is rendered kind of useless. Kind of a joke. Kind of leading one to think anyone trying to sell a solution here could be dumb or a fraud. Might be some new breakthrough, but could it?
I’m not sure - I think between the NIST tracks for age estimation and the work entities have done to gather large, diverse sample sets shows meaningful progress and perhaps real world usage.
Your points above are valid and real concerns, in addition to liveliness. There is work further to be done and improvements to be made. But it seems to me that they are solvable problems.
These datasets are getting granular, monolid vs non, 12+ different ethnicity sub groups and so forth.
Do you not think that with enough data it’s solvable?
The system I worked on had (it's larger now) 100M faces in the training set, and when I was leaving there was a 300M set in the works. We went to lengths to collect and categorize. It's mixed ethnicity that throws a wrench into ethnic categorization. It is ordinary to have people with a half dozen or more racial compositions, and that pretty much wreaks categorization. We (they) also had a a pretty robust liveness detection, and surgical mask detection with a "see through the mask" feature too (available with certain crazy-tech cameras.)
Post realizing CC can operate same code base, same file tree on different terminals instances, it's been a significant unlock for us. Most devs have 3 running concurrently. 1. master task list + checks for completion on tasks. 2. operating on current task + documentation. 3. side quests, bugs, additional context.
rinse and repeat once task done, update #1 and cycle again. Add in another CC window if need more tasks concurrently.
downside is cost but if not an issue, it's great for getting stuff done across distributed teams..
