From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Greg Stark <stark(at)mit(dot)edu> |
Cc: | "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-07-13 19:18:46 |
Message-ID: | CABUevEya3hKxgY5CwBbJf6oV9tGe0Zs=y-UCxiOqv+pyRo5naQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Wed, Jul 12, 2017 at 4:37 PM, Magnus Hagander <magnus(at)hagander(dot)net>
wrote:
>
>
> On Wed, Jul 12, 2017 at 4:35 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
>
>> On 12 July 2017 at 15:27, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> >
>> > That said, this is not intended to *replace* the username/password login
>> > part, it would be in addition to it.
>>
>> In that case I think it's actively a bad idea. If people would still
>> have to create another password there's no point and it would
>> contribute to people not wanting to use common auth schemes like this.
>>
>
> They would not have to make another password. It would be possible to
> create a community account without a password (which would then only be
> reachable through an oauth login from a supported provider).
>
>
>
>> If you just have to make a username that's not as bad (though not ideal).
>>
>
> That would be the idea.
>
>
So to show it in more detail, here is an example of the workflow of my
prototype: https://www.hagander.net/tmp/flow.ogv
(note for those reading in the archives -- link will go dead in a couple of
days)
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2017-07-13 21:30:36 | Re: Google signin |
Previous Message | Daniel Gustafsson | 2017-07-13 18:54:27 | Re: Google signin |