From: "Eric Larchevêque" <elarch@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Draft BIP for seamless website authentication using Bitcoin address
Date: Fri, 4 Apr 2014 16:56:10 +0200 [thread overview]
Message-ID: <CA+WZAEpwBqucw7kOFrRn_TsnVGaY0-hm4Xv64_i7LweEzQ=oGw@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP15xWWq2jU5yKjG+9hp___OovtbH+vM5KkzFcaQ=koRow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
On Fri, Apr 4, 2014 at 4:51 PM, Mike Hearn <mike@plan99•net> wrote:
> My view on this is mainly about the UX and the fact everyone in
>> Bitcoinland has a wallet.
>>
>
> Well, yes, but we also have browsers too :)
>
>
Yes, but no one will ever install a plug in.
And all will update their wallets with the last version, including the auth
protocol.
> I don't want to suggest the problem is unimportant - I'd love it if the
> world could move beyond passwords. But I have many scars from my time in
> the Google account swamps. We had a big team, lots of resources and even
> just getting people to use their phone as a second factor - *the simplest
> second factor possible* - was a huge uphill battle that most users just
> didn't care about. People like passwords. If you can find a way to make
> something that's better than a password but just as convenient, fantastic!
> But I don't think Bitcoin addresses are such a thing.
>
I perfectly understand all the objections, and they are very good points.
I have at least two wallets enthousiastic about the project so the protocol
will be implemented and it will give some room to experiment.
The BIP came from the idea we should formalize the standard so all wallets
could participate, and it felt more logical to come forward with it.
Maybe a better strategy would be to start "privately" with a few wallets
and services using the protocol, and to come back to the BIP there is
usability and traction.
Eric
[-- Attachment #2: Type: text/html, Size: 2752 bytes --]
next prev parent reply other threads:[~2014-04-04 14:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 12:15 Eric Larchevêque
2014-04-04 13:08 ` Mike Hearn
2014-04-04 13:22 ` Eric Larchevêque
2014-04-04 13:32 ` Gavin Andresen
2014-04-04 13:47 ` Eric Larchevêque
2014-04-07 20:08 ` Troy Benjegerdes
2014-04-07 21:55 ` Ricardo Filipe
2014-04-07 22:00 ` Eric Martindale
2014-04-04 13:43 ` Mike Hearn
2014-04-04 13:47 ` Jeff Garzik
2014-04-04 13:54 ` Mike Hearn
2014-04-04 14:42 ` Eric Larchevêque
2014-04-04 14:51 ` Mike Hearn
2014-04-04 14:56 ` Eric Larchevêque [this message]
2014-04-08 3:28 ` Jeff Garzik
2014-04-08 8:13 ` Mike Hearn
2014-04-08 15:19 ` Jeff Garzik
2014-04-22 6:34 ` Jan Møller
2014-04-22 8:57 ` Eric Larchevêque
2014-04-04 15:00 ` slush
2014-04-04 14:56 ` slush
2014-04-04 15:09 ` Eric Larchevêque
2014-04-04 15:28 ` slush
2014-04-04 15:37 ` Mike Hearn
2014-04-04 15:42 ` slush
2014-04-04 16:00 ` Eric Larchevêque
2014-04-04 15:03 ` Eric Larchevêque
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+WZAEpwBqucw7kOFrRn_TsnVGaY0-hm4Xv64_i7LweEzQ=oGw@mail.gmail.com' \
--to=elarch@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox