> Den 24. apr. 2016 kl. 20.58 skrev Claude Paroz <[email protected]>: > > - I'm afraid this change may result in boilerplate as most custom user models > will revert to Django's historical (and in my opinion sensible) username > validation rules. > > That's a tough question to estimate. This might be true for most English > monolingual web sites, but not necessarily for the majority of Django sites. > Hopefully we'll get some more user inputs in this thread.
>From a security point of view, I understand the reasoning here. Everyone >expects ASCII-only usernames. There were the same discussions when IDN was >introduced. But even with ASCII, people are attempting to spoof (googel.com, >gogle.com etc). We need a way to normalize unicode - preferably an external >library or method, since this is not a Django-specific problem. Being from .dk, we're used to translating "Åge Æbelø" to "aage_aebeloe" when creating usernames. But just like 8.3 filenames were the norm in DOS and we got around that, we now expect to be able to create long filenames with spaces and unicode characters. There was a 15-year transition period where unicode filenames would maybe work and often break things in unexpected ways (I *still* find issues from time to time). Unicode was for the brave and those with lots of free time to waste. But I think that in 2016, software that cannot handle unicode is simply broken and must be fixed. Sure, unicode can be a hassle. I still need to hexdump strings once in a while to find out what is going on. But there is no way we can continue to not support the billions of people in the world that use a language that doesn't fit into ASCII. For usernames, most people may still want the old behavior, and they can do that. It could even be the default (remember POLA). But being able to create unicode usernames should be possible and supported. Erik -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9C750A64-E218-4D76-828C-72DA3E98ECAE%40cederstrand.dk. For more options, visit https://groups.google.com/d/optout.
