Re: Google signin

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: Google signin
Date: 2017-08-28 15:34:19
Message-ID: CABUevEx-pGVwXK7SFarJuqJkQN2CbB9Feb0wRYDdOy5FT179cA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Thu, Aug 17, 2017 at 1:52 PM, Magnus Hagander <magnus(at)hagander(dot)net>
wrote:

> On Tue, Aug 15, 2017 at 11:34 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
>
>> On 15 August 2017 at 11:18, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> > On Tue, Aug 15, 2017 at 10:42 AM, Magnus Hagander <magnus(at)hagander(dot)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.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2017-08-29 08:03:22 Re: Beta testing page refers to beta2, not beta3
Previous Message Laurence Parry 2017-08-25 02:56:07 Beta testing page refers to beta2, not beta3