Besides the humor of how Lyft's filter flagged traditionally Caucasian names like "Cummings" – in addition to the usual issues with non-Western names, e.g. Pimpong and Poon – I'm fascinated/confused how this made it into production? The user database already exists and was currently being used by the live application. Before deploying this new filter onto the production database, wouldn't you do a dry run to get not…
Since a credit card is required to use Lyft, why not just validate the name on the card with the card company and make it the issuer's problem?
Which makes sense. There's likely a lot of drivers who want to go by "Tom" instead of "Thomas" or whatever their full official name is – which is even more important for drivers with very uncommon names who want to go by something more familiar/pronounceable. There's probably a decent safety argument for not requiring drivers to have their full real names be accessible to the user, especially in cases where a driver has an uncommon (i.e. easy to doxx) name.