<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-09-28&#xA;📝 Original message:&gt;&#xA;&gt; The rationale for soft vs hard-forks is well known, so I wont go over them.&#xA;&gt;&#xA;&#xA;The rationale of &#34;backwards compatibility&#34; is well known, yet wrong. I&#39;ve&#xA;gone over the arguments here and explained why the concept makes no sense:&#xA;&#xA;https://medium.com/@octskyward/on-consensus-and-forks-c6a050c792e7&#xA;&#xA;Eric - no, it&#39;s not sophisticated humour. I&#39;ve been objecting to soft forks&#xA;since this idea first appeared.&#xA;&#xA;There is no consensus. Now pick. Lose the requirement that everyone agree&#xA;for consensus changes, and tell people you&#39;ve done it. Change the spec. Or&#xA;do nothing.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150928/5dae3282/attachment.html&gt;</html></oembed>