On Tue, Aug 18, 2020 at 12:26 PM Adam Johnson <[email protected]> wrote: > > The only change we should be making is moving from separate first_name + > last_name fields to solely a name field, since *many* people don't fit into > that. I think there's a ticket, but there are massive backwards > compatibility concerns. >
This may be true - not all people have first_name & last_name or want to use them online. But it's also convenient to be able to call a person by their first name, and also allow them to use their full name on the website. I checked popular websites - Facebook and Google require first name and last name, Twitter, GitHub and Stack Overflow require only a "name", and I heard that in some IP addresses and languages Facebook doesn't require a last name, but I tried and I couldn't delete my last name from Facebook. I have a formal last name, but I want to be registered only with my first name on Facebook, which I can't. And by the way, Facebook, Twitter and Github let me change my username, Google didn't. So I have to use a username which doesn't reflect my real name on Google (I changed my last name and the username reflects my former last name). The only way to use a different username on Google is to create a new account. But also if I change my username, my email address would change, and messages sent to my previous email address might not reach me. אורי. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CABD5YeE6wmedgQk5c15ND8TU4xN4iOMyS2Cn6cEL2NJ4DBi12A%40mail.gmail.com.
