<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:2015-07-23&#xA;📝 Original message:&gt;&#xA;&gt; You complained about the lack of quantitative analysis being used, I gave&#xA;&gt; it to you. There&#39;s nothing &#34;negative&#34; about displaying data which doesn&#39;t&#xA;&gt; completely back up what your position is, I made a sensible conclusion&#xA;&gt; based on the facts I have in front of me. Ignoring the information I&#xA;&gt; collected and presented for you is incredibly childish.&#xA;&gt;&#xA;&#xA;He hasn&#39;t ignored you, and he wasn&#39;t responding to your email specifically&#xA;but rather the general attitude displayed in this forum for the last&#xA;several months (and I&#39;d argue the last year or so).&#xA;&#xA;Your data is interesting but ultimately tell us what we already know - that&#xA;the next bottleneck after the hard coded limit could easily be propagation&#xA;speed. The solution is likely to be a better protocol. Matt&#39;s custom&#xA;network already has optimised things, rolling some of those ideas into the&#xA;P2P protocol may be a good place to start, or something fancier like IBLTs.&#xA;&#xA;Regardless, the *next* bottleneck is not the protocol, it&#39;s the hard cap.&#xA;&#xA;So the conclusion remains unchanged: Bitcoin must grow, and solutions for&#xA;scaling it up will be found as the need arises.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150723/23883077/attachment.html&gt;</html></oembed>