<oembed><type>rich</type><version>1.0</version><author_name>npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_name><author_url>https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-03-21&#xA;📝 Original message:On 03/20/2014 01:12 PM, Adam Back wrote:&#xA;&#xA;&gt; Whats a sensible limit on practical/convenient QR code size?&#xA;&#xA;Technically 3 KB. In my experience codes above 1.5 KB become impossible&#xA;to scan (ZXing scanner, 3 years ago). You will want to stay below 500&#xA;bytes for convenient scanning. That said, I&#39;m convinced there is a lot&#xA;of room for scanning improvements.&#xA;&#xA;&gt; How much of the payment protocol message size comes from use of x509?&#xA;&#xA;As said in the OP, a minimal PR uses 50 bytes. X.509 seems to put about&#xA;4000 bytes on top of that.&#xA;&#xA;As you can see, we have quite some room for improvements to PR payload&#xA;(PaymentDetails). X.509 certification will probably not be possible via&#xA;QR, at least not until specialized CA&#39;s will issue space-efficient certs&#xA;(using ECDSA?).</html></oembed>