<oembed><type>rich</type><version>1.0</version><author_name>npub1rv5ajnhgrc0wq3ulrk6tcjkgsaq8h4rs5rtsvrnklz4j0lw40egqphc5wt</author_name><author_url>https://nostr.ae/npub1rv5ajnhgrc0wq3ulrk6tcjkgsaq8h4rs5rtsvrnklz4j0lw40egqphc5wt</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-18&#xA;📝 Original message:&gt;Impacts, yes, decider, no.  Multiple ACKs are required from developers &#xA;who will not act if the community will disagree with the change.&#xA;&#xA; &gt;The users ultimately choose by deciding which software to download, &#xA;and that dictates the range of choices available.&#xA;&#xA;That is what I mean by a cultish reply.  Just saying the users &#xA;ultimately decide is not an adequate explanation of the situation. You &#xA;are talking hard fork if someone doesn&#39;t like it.  If 10% of the users &#xA;don&#39;t like there is nothing they can do unless they want to operate an &#xA;altcoin.  You are not going to resolve anything by repeating these types &#xA;of replies that really have no applicability in the real world.  The &#xA;person who approves the pull request (no matter what the process is &#xA;beforehand) is effectively the decider.&#xA;&#xA;Also, as pointed out, there is no real process in place.   Making &#xA;offhand statements that &#34;multiple ACKs are required&#34; without describing &#xA;a real process just sends people down a rat hole like this block size &#xA;debate.  Providing these (non) answers instead of developing a real &#xA;process is why there is so much contention now.&#xA;&#xA;Russ</html></oembed>