From: "Jorge Timón" <jtimon@jtimon•cc>
To: John Tromp <john.tromp@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] What to do when contentious soft fork activations are attempted
Date: Sat, 7 May 2022 03:57:39 +0200 [thread overview]
Message-ID: <CABm2gDrJCo02E8AtJwGQ2jfJokeG9dMuxrO44kT9m1GZZ+1Z2w@mail.gmail.com> (raw)
In-Reply-To: <CAOU__fwuT8tuV+5KG28toxQO1kwgm0S7CHtsQrZqx7my9RwCtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
It is quite ironic that yeah, it is quite ironic that the people who are
constantly basing their arguments on personal attack are also the ones who
complain the most about personal attacks. That's exactly the irony I was
trying to convey.
Just like some people claim that the only people against bip119 are people
ignorant about bip119, I can also claim that everyone against bip8 doesn't
really understand it, can't I?
The same people who spread the misinformation that bip8 "would be perceived
by most users as developers trying to dictate changes" are now complaining
about people spreading misinformation about their own proposals. I
personally find it as ironic as it can get.
I'm glad I'm not the only one who noticed how ironic the whole situation is.
How often are the people claiming to be concerned about misinformation
precisely the ones who spread the most misinformation?
Very ironic indeed.
On Fri, May 6, 2022 at 10:07 PM John Tromp via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> On Fri, 6 May 2022 7:17PM Jorge Tim?n wrote
> > But let's not personally attack andreas for his opinions.
> > The only reason you don't like bip8 is because you're ignorant about it
> and
> > you haven't reviewed it enough.
>
> Can you see the irony in equating "clueless about BIP119" with a
> personal attack and then calling Jeremy ignorant about BIP8?
>
> -John
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2214 bytes --]
next prev parent reply other threads:[~2022-05-07 1:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.53264.1651860071.8511.bitcoin-dev@lists.linuxfoundation.org>
2022-05-06 19:58 ` John Tromp
2022-05-07 1:57 ` Jorge Timón [this message]
2022-04-30 9:53 Michael Folkson
2022-05-01 1:20 ` alicexbt
2022-05-01 12:47 ` Jorge Timón
2022-05-03 14:36 ` Ryan Grant
2022-05-06 17:17 ` Jorge Timón
2022-05-06 18:23 ` Russell O'Connor
2022-05-06 22:44 ` Jorge Timón
2022-05-01 19:14 ` Billy Tetrud
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=CABm2gDrJCo02E8AtJwGQ2jfJokeG9dMuxrO44kT9m1GZZ+1Z2w@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=john.tromp@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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