On Thu, Aug 17, 2017 at 1:52 PM, Magnus Hagander <magnus@hagander.net> wrote:
On Tue, Aug 15, 2017 at 11:34 PM, Greg Stark <stark@mit.edu> wrote:
On 15 August 2017 at 11:18, Magnus Hagander <magnus@hagander.net> wrote: > On Tue, Aug 15, 2017 at 10:42 AM, Magnus Hagander <magnus@hagander.net> > wrote: > > Here's an updated patch that does this. It will try in order: > <firstname><lastinitial>, e.g. stephenf > <firstinitial><lasdtname>,e.g. sfrost > <firstname><lastinitial><number>, e.g. stephenf0, stephenf1, stephenf2 etc
Taking just the first name or just the last name and a number seems fairly safe but anything that combines letters runs the risk of creating unintentionally offensive words.
That's a good point. OTOH the user still gets a chance to change it before they accept it, so they can easily fix that. (And we don't generally have a filter for users who intentionally pick offensive words as their logins)
The latest version of this with some minor bugfixes has now been deployed.
