From: Ryan Grant <bitcoin-dev@rgrant.org>
To: "Jorge Timón" <jtimon@jtimon.cc>,
"Michael Folkson" <michaelfolkson@protonmail.com>,
"Bitcoin Protocol Discussion"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] User Resisted Soft Fork for CTV
Date: Sun, 24 Apr 2022 12:55:22 +0000 [thread overview]
Message-ID: <CAMnpzfr79gV=mrN_=hFr064HwzyNjSYRN1pP=Tx7vabjT6fV5A@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDpb4LmLh3LMy1Z4uAWyKp-9AqUKc2DzcxZa7VPqqUVddQ@mail.gmail.com>
Michael and Jorge,
It is ethically inappropriate to make personal attacks on the
trustworthiness of participants on this list, on such vague grounds as
disliking an activation proposal!
https://en.wikipedia.org/wiki/Wikipedia:Assume_good_faith
It is against the spirit of the project to base your judgements of a
technical solution on who presents them! You should not be so
technically adrift that you only have reputation left to speak about.
If you disagree with ideas, then shoot them down on the technical merits.
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-October/011457.html
If you disagree with people, then take it to smuttier sections of the Internet.
next prev parent reply other threads:[~2022-04-24 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 16:45 [bitcoin-dev] User Resisted Soft Fork for CTV Michael Folkson
2022-04-21 23:36 ` Keagan McClelland
2022-04-22 9:03 ` Zac Greenwood
2022-04-22 15:40 ` Corey Haddad
2022-04-23 5:07 ` Billy Tetrud
2022-04-23 14:48 ` Erik Aronesty
2022-04-24 14:47 ` Peter Todd
2022-04-25 5:36 ` ZmnSCPxj
2022-04-25 9:06 ` Zac Greenwood
2022-04-25 10:01 ` ZmnSCPxj
2022-04-22 9:53 ` Michael Folkson
2022-04-23 20:40 ` Jorge Timón
2022-04-24 12:17 ` Michael Folkson
2022-04-24 12:57 ` Jorge Timón
2022-04-24 12:55 ` Ryan Grant [this message]
2022-04-24 13:11 ` Jorge Timón
2022-04-24 13:15 ` Ryan Grant
2022-04-25 16:11 alicexbt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMnpzfr79gV=mrN_=hFr064HwzyNjSYRN1pP=Tx7vabjT6fV5A@mail.gmail.com' \
--to=bitcoin-dev@rgrant.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jtimon@jtimon.cc \
--cc=michaelfolkson@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox