{"type":"rich","version":"1.0","author_name":"npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n","author_url":"https://nostr.ae/npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-03-28\n📝 Original message:On Tuesday, March 28, 2017 8:53:30 PM Alphonse Pace via bitcoin-dev wrote:\n\u003e His demand (not suggestion) allows it without any safeguards.\n\u003e \n\u003e \u003eThis patch must be in the immediate next release of Bitcoin Core.\n\u003e \n\u003e That is not a suggestion.\n\nI think it was probably a design requirement more than a demand. It makes \nsense: if we're aiming to have a long lead time for a possible hardfork, we \nwant to get the lead time started ASAP. (It could perhaps have been \ncommunicated clearer, but let's not read hostility into things when \nunnecessary.)\n\nMeta-topic: Can we try a little harder to avoid sequences of multiple brief \nreplies in a matter of minutes? Combine them to a single reply.\n\nLuke"}