From: Mike Hearn <mike@plan99•net>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP21 bitcoin URIs and HTML5
Date: Thu, 2 May 2013 14:53:38 +0200 [thread overview]
Message-ID: <CANEZrP3v_5ZJgnn4Qbam6d23BYKeHdvaReDV9dsVyC1tGenb8w@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgRtq5J4HAeQGTfKc+vQZ9eo1Qw4nc=t2_Pu3KAuE_3WGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
Chrome has whitelisted bitcoin: URIs for web apps, and Firefox it turns out
doesn't use whitelisting at all, so it already works there.
https://chromiumcodereview.appspot.com/14531004
I'm hoping this means web wallet developers won't be put off from
supporting the payment protocol (that risk is the reason I started this
work).
The next step is to file bugs against WebKit (for Safari/iOS/misc other
platforms), and IE, though I don't know if Microsoft uses open bug trackers
much.
On Wed, Apr 24, 2013 at 6:37 PM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
> On Wed, Apr 24, 2013 at 7:51 AM, Gavin Andresen <gavinandresen@gmail•com>
> wrote:
> >> Ian pointed out some errors in the BIP21 spec. What's the process for
> >> amending the BIP? Do we need to create a new one and mark the old one as
> >> replaced, or can we just fix it in place given the relatively exotic
> nature
> >> of most of the issues?
> > Those all sound like bugs in the BIP; I think they should just be fixed,
> I
> > don't think we need a new BIP.
>
> Yup. Corrections are fine, esp ones which are not gratuitously
> incompatible.
>
[-- Attachment #2: Type: text/html, Size: 1738 bytes --]
next prev parent reply other threads:[~2013-05-02 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 7:42 Mike Hearn
2013-04-24 13:35 ` Andreas Schildbach
2013-04-24 14:51 ` Gavin Andresen
2013-04-24 16:37 ` Gregory Maxwell
2013-05-02 12:53 ` Mike Hearn [this message]
2013-04-24 16:21 ` Melvin Carvalho
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=CANEZrP3v_5ZJgnn4Qbam6d23BYKeHdvaReDV9dsVyC1tGenb8w@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/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