<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated></updated>
  <generator>https://nostr.ae</generator>

  <title>Nostr notes by </title>
  <author>
    <name></name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://nostr.ae/npub1f6lcnu5cs3nhzxnw7pmgq9lny6tpa93qdq932ay7epqjqpn5rq6s8jcphu.rss" />
  <link href="https://nostr.ae/npub1f6lcnu5cs3nhzxnw7pmgq9lny6tpa93qdq932ay7epqjqpn5rq6s8jcphu" />
  <id>https://nostr.ae/npub1f6lcnu5cs3nhzxnw7pmgq9lny6tpa93qdq932ay7epqjqpn5rq6s8jcphu</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://nostr.ae/nevent1qqstwdsu7fm3fyk7nkg7u3cygdhxtp4xs3ykwv6m62tmkyvduzpng0gzyp8tlz0jnzzxwug6dmc8dqqh7vnfv85kyp5qk9t5nmyyzgqxwsvr29spdt2</id>
    
      <title type="html">📅 Original date posted:2018-04-09 📝 Original message: Hi ...</title>
    
    <link rel="alternate" href="https://nostr.ae/nevent1qqstwdsu7fm3fyk7nkg7u3cygdhxtp4xs3ykwv6m62tmkyvduzpng0gzyp8tlz0jnzzxwug6dmc8dqqh7vnfv85kyp5qk9t5nmyyzgqxwsvr29spdt2" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqszhelapgwxcvc2n39rjzqe3hv7yy3z8yuxukyvkz65pqu5vqq6rfsf26chp&#39;&gt;nevent1q…6chp&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;📅 Original date posted:2018-04-09&lt;br/&gt;📝 Original message:&lt;br/&gt;Hi all,&lt;br/&gt;&lt;br/&gt;On 9 April 2018 at 11:47, Corné Plooy via Lightning-dev &amp;lt;&lt;br/&gt;lightning-dev at lists.linuxfoundation.org&amp;gt; wrote:&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; Is this really only about reducing the size of QR codes? How many&lt;br/&gt;&amp;gt; percent reduction do you think you can accomplish with your approach? I&lt;br/&gt;&amp;gt; think, when it comes to reducing QR code size, it makes more sense to&lt;br/&gt;&amp;gt; think of a better way to encode the node ID. Hexadecimal isn&amp;#39;t exactly&lt;br/&gt;&amp;gt; the most space-efficient encoding.&lt;br/&gt;&amp;gt;&lt;br/&gt;&lt;br/&gt;We&amp;#39;d save 33 bytes by not using hex. Makes the QR code a bit rarer&lt;br/&gt;(whatever is opposite of dense).&lt;br/&gt;I intend to support both approaches, if there are 33 bytes before the &amp;#39;@&amp;#39;&lt;br/&gt;it&amp;#39;s raw, 66 it&amp;#39;s hex.&lt;br/&gt;&lt;br/&gt;Igor&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&amp;gt; Op 07-04-18 om 17:17 schreef Robert Olsson:&lt;br/&gt;&amp;gt; &amp;gt; Hello all,&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; I seem to not find a bolt regarding the QR code of node at ip:port&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; It seems eclair only supports the format hex at ip:port format, and i&lt;br/&gt;&amp;gt; &amp;gt; haven&amp;#39;t tried any other mobile wallets.&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; I thought there would be support for bech32 nodeid:s to keep the QR&lt;br/&gt;&amp;gt; &amp;gt; small, but it doesn&amp;#39;t seem that way.&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; If it isn&amp;#39;t standardized yet, i think we should do it soon so all&lt;br/&gt;&amp;gt; &amp;gt; wallets will support it from start and we can avoid bulky QR codes.&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; To fully utilize QR it should work with charset in text-mode, so i&lt;br/&gt;&amp;gt; &amp;gt; would suggest a format like&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; lightning:ln1bech32nodeid/ipnumber/port&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; where /port is optional if port is 9735&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; this is to avoid @ and confusion of : in ipv6 and :portnumber&lt;br/&gt;&amp;gt; &amp;gt; (skip &amp;#39;[&amp;#39; and &amp;#39;]&amp;#39; in ipv6)&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; another approach would be to encode ip and portnumber in bech32 as&lt;br/&gt;&amp;gt; &amp;gt; well. my opinion is that everything coded entirely in bech32 shouldn&amp;#39;t&lt;br/&gt;&amp;gt; &amp;gt; need a protocol so the &amp;#39;lightning:&amp;#39; part could possibly be omitted as&lt;br/&gt;&amp;gt; &amp;gt; well.&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; or did i just miss a bolt somewhere?&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; best regards&lt;br/&gt;&amp;gt; &amp;gt; Robert Olsson&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt;&lt;br/&gt;&amp;gt; &amp;gt; _______________________________________________&lt;br/&gt;&amp;gt; &amp;gt; Lightning-dev mailing list&lt;br/&gt;&amp;gt; &amp;gt; Lightning-dev at lists.linuxfoundation.org&lt;br/&gt;&amp;gt; &amp;gt; &lt;a href=&#34;https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev&#34;&gt;https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev&lt;/a&gt;&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; _______________________________________________&lt;br/&gt;&amp;gt; Lightning-dev mailing list&lt;br/&gt;&amp;gt; Lightning-dev at lists.linuxfoundation.org&lt;br/&gt;&amp;gt; &lt;a href=&#34;https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev&#34;&gt;https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev&lt;/a&gt;&lt;br/&gt;&amp;gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;-- &lt;br/&gt;*Igor Cota*&lt;br/&gt;Codex Apertus Ltd&lt;br/&gt;-------------- next part --------------&lt;br/&gt;An HTML attachment was scrubbed...&lt;br/&gt;URL: &amp;lt;&lt;a href=&#34;http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180409/eb71167a/attachment.html&amp;gt&#34;&gt;http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180409/eb71167a/attachment.html&amp;gt&lt;/a&gt;;
    </content>
    <updated>2023-06-09T12:49:47Z</updated>
  </entry>

</feed>