<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-09-25&#xA;📝 Original message:We could also say that if protocol part (https://) is missing, it&#39;s implied&#xA;automatically. So just:&#xA;&#xA;bitcoin:1abc........?r=bob.com/r/aZgR&#xA;&#xA;I think that&#39;s about as small as possible without re-using the pubkey as a&#xA;token in the url.&#xA;&#xA;&#xA;On Wed, Sep 25, 2013 at 1:35 AM, Gavin Andresen &lt;gavinandresen at gmail.com&gt;wrote:&#xA;&#xA;&gt; On Tue, Sep 24, 2013 at 11:52 PM, Mike Hearn &lt;mike at plan99.net&gt; wrote:&#xA;&gt;&#xA;&gt;&gt; BTW, on the &#34;make qrcodes more scannable&#34; front -- is it too late to&#xA;&gt;&gt; change BIP 72 so the new param is just &#34;r&#34; instead of &#34;request&#34;? Every byte&#xA;&gt;&gt; helps when it comes to qrcodes ...&#xA;&gt;&gt;&#xA;&gt;&#xA;&gt; Not too late, assuming there are no objections. Smaller QR codes is a very&#xA;&gt; good reason to change it.&#xA;&gt;&#xA;&gt; --&#xA;&gt; --&#xA;&gt; Gavin Andresen&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130925/342acca1/attachment.html&gt;</html></oembed>