Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id BD522C000B for ; Fri, 18 Mar 2022 18:36:18 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id A59D6417AE for ; Fri, 18 Mar 2022 18:36:18 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=jtimon-cc.20210112.gappssmtp.com Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rs55ljkOnvYp for ; Fri, 18 Mar 2022 18:36:16 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) by smtp4.osuosl.org (Postfix) with ESMTPS id 7F8D341766 for ; Fri, 18 Mar 2022 18:36:16 +0000 (UTC) Received: by mail-yb1-xb31.google.com with SMTP id t11so17332713ybi.6 for ; Fri, 18 Mar 2022 11:36:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jtimon-cc.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KbhrrQddVgbKTQRjmABN/s0Tk5Viu0nshwxTOMIMlos=; b=KxJIYjAxH71OYkC8i9fURmagOklh8JyzCwkad5jt2Wvfa9GqLgvCrtSM/UiDScZXhN GP1gvu9DF10gV4bUtuj25aeUsic/DQsULynnlJbquvGNueE+aw5sb8L4VZS5ug2sHxVO GVa/Pqvbe73Dzj8U48mQOCqRQAyJK65csr+CwH+hORA5gGbC0TIqqDDUrBP3Nztv09YX 2PCFPnWPpRWKiLfK0+15SQLgQJDOhxVvXKvdU40+9ZNj6CswEmb65xecXWliUnVx1VNn ceEe1ClQCiq3BgxzHZyjTIBclW5FGCLUkEP/1V3+q59UX3GsXh+yKJYh0fbavfySkeyp XDUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KbhrrQddVgbKTQRjmABN/s0Tk5Viu0nshwxTOMIMlos=; b=RK56FVCB7Gv36BDzWK8A9BzkbrO82h2P06ujxEo4FQEXq1bo6VhuqzZPhmM1VH9df6 jUYRY5wtImzuZO1CJlUV8UJSdoRpPniK7HSuaM7oqXSAYf19ZD/mvGWO/pcKJhHFdNqa 6lPWDY8iFp5PikeUSUa33Ik/mLZtB8HofzOTyLBO1sMUIm5QLuvSPrDozM4Nxtye+Feg pA2C54a1e2lIfDdQw37QcnjHAOfVjkD9Urt1SBO9aPvSJFnBWxsUF3lZADrR07WI4TeR YdByaHJvbLVWe0lkL1+JgWZqlFCzixtbKGZcxd+EEy4E4eCv+nBfxsAz84s/trGh19zZ 1Liw== X-Gm-Message-State: AOAM532vs9+nEbZnX47NxgtYzlssI8LNytvQBezKDSvDg8hUfTxK77MS MLTmcGvPNGVeVaG4BYbq3PuqviOBzRcg56GYpzDumg== X-Google-Smtp-Source: ABdhPJymkUdc5gIrdkv7RPoF9WlI4udBS01EVlgT+EBmcImX87WhVcu7++vzLwOM56urFtwQNVStNf3HZh9ghXKohl8= X-Received: by 2002:a5b:7d1:0:b0:628:d9f7:c5b8 with SMTP id t17-20020a5b07d1000000b00628d9f7c5b8mr11888222ybq.347.1647628575316; Fri, 18 Mar 2022 11:36:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= Date: Fri, 18 Mar 2022 19:36:03 +0100 Message-ID: To: Jeremy Rubin , Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Fri, 18 Mar 2022 18:51:16 +0000 Subject: Re: [bitcoin-dev] Speedy Trial X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2022 18:36:18 -0000 On Tue, Mar 15, 2022 at 6:25 PM Jeremy Rubin via bitcoin-dev wrote: > > Boker tov bitcoin devs, I don't undesrtand what that means, sorry >> A mechanism of soft-forking against activation exists. What more do you want? > > > Agreed -- that should be enough. No, resistance should ideally be a priori, not a posteriori. > >> >> Are we supposed to write the code on behalf of this hypothetical group of users who may or may not exist for them just so that they can have a node that remains stalled on Speedy Trial lockin? >> >> That simply isn't reasonable, but if you think it is, I invite you to create such a fork. > > > Disagree. > > It is a reasonable ask. > > I've done it in about 40 lines of python: https://github.com/jeremyrubin/forkd > > Merry Christmas Jorge, please vet the code carefully before running. 40 lines of python code should be easy to bet even if the author was very bad at writing readable code and obfuscated his code on purpose. I don't know if it's the case, because, sorry, I'm not reviewing your code at the moment. "Vet the code carefully before running" strikes me as arrogant and condescending. as if you were implying my engineering capacity was very limited. If you say these things to me publicly, I can only only imagine what you have told other devs behind my back about my capacity (or even my ideology) if they ever asked (or perhaps without them asking). I really hope you haven't lied to anyone about my ideology, J. Perhaps I do have "prosectution complex" with you indeed. Not with Russel, but with you. After all, I've publicly say I don't trust you, haven't I? But, again, what do I know about psychology? Going back on topic, the reason I won't review your code is because you have rushed a design before understanding the analysis. No, I'm not asking for a stalled mechanism for speedy trial, I don't want speedy trial. We disagree on the analysis of the problem to solve, that's why we disagree on the design for the solution. https://en.wikipedia.org/wiki/Systems_development_life_cycle#Analysis Anyway, perhaps I look at the code in the future if your proposal consensus change seems to prosper. Regarding "merry christmas"...what the f are you talking about? it's not Christmas time and neither you or me are christians, are you? If this is some sort of riddle or joke, we really must have very different senses of humor, because I don't get it. Come on, J, let's both try to stay on topic or people will start to correctly point out that we both negatively discriminate each other for offtopic reasons, be them reasonably justified or not. > Peace, Ama, y ensancha el alma. > Jeremy > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev