<oembed><type>rich</type><version>1.0</version><author_name>npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_name><author_url>https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-04-24&#xA;📝 Original message:HTML5 allows web apps to register themselves for handling URI schemes, such&#xA;as the bitcoin: URI that is already in use and being extended as part of&#xA;the payment protocol.&#xA;&#xA;The bad news is that for security reasons there is a whitelist of&#xA;acceptable schemes in the spec:&#xA;&#xA;http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#dom-navigator-registerprotocolhandler&#xA;&#xA;The good news is that yesterday I talked to Hixie about it and he added&#xA;bitcoin to the whitelist:&#xA;&#xA;http://html5.org/tools/web-apps-tracker?from=7849&amp;to=7850&#xA;&#xA;I&#39;m currently finding out what the process is for browser makers to notice&#xA;the change (perhaps they watch the spec commit history and nothing needs to&#xA;be done), but within a few months most users should have browsers that can&#xA;accept bitcoin as a web-app handleable protocol scheme. I suppose IE10&#xA;users may be the laggards, but I guess we can live with that for now.&#xA;&#xA;Ian pointed out some errors in the BIP21 spec. What&#39;s the process for&#xA;amending the BIP? Do we need to create a new one and mark the old one as&#xA;replaced, or can we just fix it in place given the relatively exotic nature&#xA;of most of the issues? Here&#39;s his feedback:&#xA;&#xA;&#xA;- BNF doesn&#39;t say what it&#39;s character set is (presumably it&#39;s Unicode)&#xA;&#xA; - &#34;bitcoinparams&#34; production doesn&#39;t define the separator, so in theory&#xA;the syntax is ...?label=foomessage=fooother=foo (rather than&#xA;...?label=foo&amp;message=foo etc)&#xA;&#xA;- the syntax allows ?amount=FOO&amp;amount=1.1 as far as I can tell, since&#xA;&#34;otherparam&#34; matches any name followed by any value, including &#34;amount&#34;&#xA;followed by a bogus value.&#xA;&#xA;- &#34;pchar&#34; is referenced without definition.&#xA;&#xA;- the &#34;simpler&#34; syntax is just wrong (it would result in&#xA;bitcoin:address?amount=1?label=FOO rather&#xA;than bitcoin:address?amount=1&amp;label=FOO)&#xA;&#xA;BTW the IETF URL specs are being obsoleted by http://url.spec.whatwg.org/,&#xA;at least for Web purposes. In that case matters.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130424/a844b4a5/attachment.html&gt;</html></oembed>