<oembed><type>rich</type><version>1.0</version><title>Gregory Maxwell [ARCHIVE] wrote</title><author_name>Gregory Maxwell [ARCHIVE] (npub1f2…crwet)</author_name><author_url>https://yabu.me/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>📅 Original date posted:2018-06-21&#xA;📝 Original message:On Thu, Jun 21, 2018 at 7:56 PM, Peter D. Gray via bitcoin-dev&#xA;&lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; PSBT is something we need, and has been missing from the ecosystem&#xA;&gt; for a long time. Let&#39;s push this out and start talking about future&#xA;&gt; versions after we learn from this one.&#xA;&#xA;When you implement proposals that have little to no public discussion&#xA;about them you take the risk that your work needs to be changed when&#xA;other people do actually begin reviewing the work.  It is incredibly&#xA;demoralizing as a designer and a reviewer to have proposals that were&#xA;put out for discussion show up implemented in things with these vested&#xA;interests then insisting that they not be refined further.  I think&#xA;kind of handling is toxic to performing development in public.&#xA;&#xA;Although it&#39;s silly enough that it won&#39;t happen, I think our industry&#xA;would be better off if there was a social norm that anytime someone&#xA;insists an unfinished proposal shouldn&#39;t be changed because they&#xA;already implemented it that the spec should _always_ be changed, in&#xA;order to discourage further instances of that conduct.</html></oembed>