Using email as Name when there is no first/last name causes information leak

The model of using an email address as the Name column in search results causes very undesirable results in some situations.

There are many cases in which we want search results for something to be public, but only the names, not the email addresses. In some of those cases, we don't want first/last name to be a required field.

As things are now, when first/last are not entered, the email address will appear publicly visible.

In these cases, records with no actual name should probably not be displayed in the public listing, or they should be displayed with a default placeholder name.

In fact, public or not, I'd suggest that email never be treated as Name, because, well, it's not, and having the software dynamically do that sometimes will inevitably cause other problems than this one.