<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-05-07&#xA;📝 Original message:&gt; The only answer to this that anyone with a clue should give is &#34;it&#xA;&gt; will very, very likely be able to support at least 1MB blocks roughly&#xA;&gt; every 10 minutes on average for the next eleven years, and it seems&#xA;&gt; likely that a block size increase of some form will happen at some point in&#xA;&gt; the next eleven years&#34;, anything else is dishonest.&#xA;&#xA;&#xA;Matt, you know better than that. Gavin neither lacks clue nor is he&#xA;dishonest.&#xA;&#xA;He has been working on the assumption that other developers are reasonable,&#xA;and some kind of compromise solution can be found that everyone can live&#xA;with. Hence trying to find a middle ground, hence considering and writing&#xA;articles in response to every single objection raised. Hence asking for&#xA;suggestions on what to change about the plan, to make it more acceptable.&#xA;What more do you want, exactly?&#xA;&#xA;And I&#39;ll ask again. Do you have a *specific, credible alternative*? Because&#xA;so far I&#39;m not seeing one.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150507/55e48fed/attachment.html&gt;</html></oembed>