Luke Dashjr [ARCHIVE] on Nostr: ๐
Original date posted:2017-03-28 ๐ Original message:On Tuesday, March 28, 2017 ...
๐
Original date posted:2017-03-28
๐ Original message:On Tuesday, March 28, 2017 8:53:30 PM Alphonse Pace via bitcoin-dev wrote:
> His demand (not suggestion) allows it without any safeguards.
>
> >This patch must be in the immediate next release of Bitcoin Core.
>
> That is not a suggestion.
I think it was probably a design requirement more than a demand. It makes
sense: if we're aiming to have a long lead time for a possible hardfork, we
want to get the lead time started ASAP. (It could perhaps have been
communicated clearer, but let's not read hostility into things when
unnecessary.)
Meta-topic: Can we try a little harder to avoid sequences of multiple brief
replies in a matter of minutes? Combine them to a single reply.
Luke
Published at
2023-06-07 17:58:14Event JSON
{
"id": "e88204ac6de77458fdc0b35a87b112ee2af241de111d86876182b9286b89e53f",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686160694,
"kind": 1,
"tags": [
[
"e",
"f66fb8ea0b053d3b896ce377aea38775ffc7975376c3ee96291861cf920b456b",
"",
"root"
],
[
"e",
"bc784c074fef4e7a0ad2f2c34f5c54055d0075b99d8e7fc7df6e8c35bd815e46",
"",
"reply"
],
[
"p",
"335bc87247c1320e83bf03c56ff52c6a06ad057152deb6038ea6f6e73b716e6f"
]
],
"content": "๐
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",
"sig": "8363932403554b3d990ff009df2297de97989a87cc5223882c0c026cef80342b7e33241e6109bc656644679780763776b2f8f0f5b3b30cb26202737ad192ffa3"
}