<oembed><type>rich</type><version>1.0</version><author_name>npub1azvhdrf9fu6n0tm7yez4j6zcxcedp2ct6nrcq3z74naqs7kgpk8s5t2krq</author_name><author_url>https://nostr.ae/npub1azvhdrf9fu6n0tm7yez4j6zcxcedp2ct6nrcq3z74naqs7kgpk8s5t2krq</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-09-28&#xA;📝 Original message:My initial reaction is just HUH?!?!? Is this some sophisticated form of humor I&#39;m just not getting?&#xA;&#xA;On September 28, 2015 3:48:57 AM PDT, Mike Hearn via bitcoin-dev &lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt;There is *no* consensus on using a soft fork to deploy this feature. It&#xA;&gt;will result in the same problems as all the other soft forks - SPV&#xA;&gt;wallets&#xA;&gt;will become less reliable during the rollout period. I am against that,&#xA;&gt;as&#xA;&gt;it&#39;s entirely avoidable.&#xA;&gt;&#xA;&gt;Make it a hard fork and my objection will be dropped.&#xA;&gt;&#xA;&gt;Until then, as there is no consensus, you need to do one of two things:&#xA;&gt;&#xA;&gt;1) Drop the &#34;everyone must agree to make changes&#34; idea that people here&#xA;&gt;like to peddle, and do it loudly, so everyone in the community is&#xA;&gt;correctly&#xA;&gt;informed&#xA;&gt;&#xA;&gt;2) Do nothing&#xA;&gt;&#xA;&gt;&#xA;&gt;------------------------------------------------------------------------&#xA;&gt;&#xA;&gt;_______________________________________________&#xA;&gt;bitcoin-dev mailing list&#xA;&gt;bitcoin-dev at lists.linuxfoundation.org&#xA;&gt;https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev&#xA;&#xA;-- &#xA;Sent from my Android device with K-9 Mail. Please excuse my brevity.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150928/0eabc6d7/attachment.html&gt;</html></oembed>