From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Aymeric Vitte <aymeric@peersm•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot NACK
Date: Wed, 17 Mar 2021 04:19:28 +0000 [thread overview]
Message-ID: <wOCt6DJ8N_0A9iJ43wTFj_4bR7DorXrB6cIGPsPBr6G_qNDP6veoDOVXnu_9wiKT2prQtbcLApzos7dSBXsaU--bv88m4xLXC8PVwpgRIvQ=@protonmail.com> (raw)
In-Reply-To: <93d634e2-4102-78f6-c5bc-48fd2af10666@peersm.com>
> It's incredible how this troll keeps trolling and the list (bitcoin-dev !!) keeping attention
>
> Good troll, really
Depending on topic raised, it may be useful to at least answer the troll naively as if it were an honest question, if only so that third parties reading do not get confused and think the troll is bringing up some objection that is actually relevant.
For this particular topic you replied to, it seems to me obviously inane to discuss the "lordship" and "majesty" of the troll.
Even if the claims to such "lordship" are *true*, for most of the world, the relevance of the previous British empire is little more than a reality TV show about the British royal family (oh, some random thing happened to some random descendant of the royal family, how interesting, say did you see that nice new (actually old) technique Jeremy was talking about on the other thread about delegating control of coins to script, it looks like "graftroot without a softfork"?), and any particular claims to nobility or aristocracy are largely moot, thus not worth answering.
Regards,
ZmnSCPxj
next prev parent reply other threads:[~2021-03-17 4:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 3:23 LORD HIS EXCELLENCY JAMES HRMH
2021-02-27 16:14 ` Jeremy
2021-02-28 11:36 ` LORD HIS EXCELLENCY JAMES HRMH
2021-02-28 13:07 ` Ariel Lorenzo-Luaces
2021-03-01 1:34 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-01 22:37 ` Eric Voskuil
2021-03-02 1:16 ` Daniel Edgecumbe
2021-03-03 3:06 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-03 11:58 ` eric
2021-03-03 16:30 ` micaroni
2021-03-03 14:49 ` Erik Aronesty
2021-03-04 5:06 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-05 14:04 ` Ryan Grant
2021-03-10 6:34 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-11 0:47 ` Keagan McClelland
2021-03-12 13:04 ` R E Broadley
2021-03-12 22:30 ` Eric Voskuil
2021-03-14 10:13 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-14 18:41 ` Aymeric Vitte
2021-03-17 4:19 ` ZmnSCPxj [this message]
2021-03-17 5:46 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-17 7:14 ` Eric Voskuil
2021-03-02 11:56 ` Chris Belcher
2021-03-03 11:22 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-16 2:11 ` ZmnSCPxj
2021-03-16 11:39 ` DA Williamson
2021-03-17 4:11 ` ZmnSCPxj
2021-03-17 8:13 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-17 9:32 ` ZmnSCPxj
2021-03-18 1:10 ` DA Williamson
2021-03-03 2:54 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-03 11:55 ` eric
2021-03-04 4:53 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-03 14:32 ` Thomas Hartman
2021-03-04 5:05 ` LORD HIS EXCELLENCY JAMES HRMH
[not found] <SL2P216MB008922741210CC853A51A5A19D979@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM>
2021-03-04 7:46 ` Eric Voskuil
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='wOCt6DJ8N_0A9iJ43wTFj_4bR7DorXrB6cIGPsPBr6G_qNDP6veoDOVXnu_9wiKT2prQtbcLApzos7dSBXsaU--bv88m4xLXC8PVwpgRIvQ=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=aymeric@peersm$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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