public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Tom Zander <tomz@freedommail.ch>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] This thread is not about the soft/hard fork technical debate
Date: Mon, 5 Oct 2015 19:41:30 +0000	[thread overview]
Message-ID: <CAAS2fgSyWaRfXHKWZYzZ4X8ksMECaO47dTXum67XwpTTYnbDXg@mail.gmail.com> (raw)
In-Reply-To: <1489086.kGfJeeyi4a@garp>

On Mon, Oct 5, 2015 at 7:13 PM, Tom Zander via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> It is an eloquent change, but not really the topic we were discussing. It also
> makes you attack Mike (calling him out as having a strawman) without basis.
> For the second time in this thread.
> I would suggest arguing on the topic, not on the man.

Such a shame you appear to reserve that wisdom for those you disagree
with, biting your tongue when others emit all forms of ad hominem--
such as suggesting we've spent less volunteer time on Bitcoin and thus
our opinion has less merit (or that we haven't written certian kinds
of software (even when, ironically, we have!), and thus our opinion
doesn't have merit, and so on). I think everyone would benefit from
it, especially as that kind of correction is best received from
someone who agrees with you.

In this case, I think, however your correction is also misplaced at
least on this message; though I would otherwise welcome it.  I'm not
complaining about the man; but pointing out the behavior of stating an
opinion no one as held as theirs and attacking it is not a productive
way to hold a discussion. It's an argument or a behavior, not a
person, and beyond calling it bad I attempted to explaining (perhaps
poorly) why its bad.

What Sergio is saying is not the same; Mike argued some established
criteria existed where it didn't-- and I was pointing that out; and
talking about how the situation here is not very similar to the one
that Mike was trying to draw a parallel to. I enumerated a number of
specific reasons why this is the case. If the differences between
Sergio's comments and mine are still unclear after this clarification,
I'd be glad to talk it through with you off-list-- in spite of your
(welcome) compliments, communication is just fundamentally difficult,
and no amount eloquence changes that. If there is continued
misunderstanding, I do not doubt its my fault; but it's probably not a
good use of hundreds/thousands of people's time for you to help me
interactively improve my explanation on list. :)


  reply	other threads:[~2015-10-05 19:41 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 15:56 [bitcoin-dev] This thread is not about the soft/hard fork technical debate Sergio Demian Lerner
2015-10-05 16:39 ` NxtChg
2015-10-05 16:51 ` Luke Dashjr
2015-10-05 16:56 ` Mike Hearn
2015-10-05 17:01   ` Paul Sztorc
2015-10-05 17:33     ` Peter R
2015-10-05 17:56       ` NxtChg
2015-10-05 22:56       ` Btc Drak
2015-10-05 23:05         ` Milly Bitcoin
2015-10-05 17:35   ` Btc Drak
2015-10-06 18:23   ` Venzen Khaosan
2015-10-06 18:28     ` Venzen Khaosan
2015-10-06 19:34       ` naama.kates
2015-10-05 17:03 ` Btc Drak
2015-10-05 17:26   ` Tom Zander
2015-10-05 17:52     ` Btc Drak
2015-10-05 18:04     ` Gregory Maxwell
2015-10-05 18:33       ` Tom Zander
2015-10-05 18:50         ` NotMike Hearn
2015-10-05 17:33 ` s7r
2015-10-05 18:51   ` Tom Zander
2015-10-05 18:35 ` Gregory Maxwell
2015-10-05 19:13   ` Tom Zander
2015-10-05 19:41     ` Gregory Maxwell [this message]
2015-10-05 20:05       ` Steven Pine
2015-10-05 20:21         ` Milly Bitcoin
2015-10-06  7:17           ` cipher anthem
2015-10-06  7:20             ` Eric Lombrozo
2015-10-06  7:29               ` Marcel Jamin
2015-10-06  8:34                 ` NotMike Hearn
2015-10-06 19:40                   ` naama.kates
2015-10-05 20:28         ` Santino Napolitano
2015-10-05 20:35       ` Tom Zander
2015-10-05 20:54         ` Dave Scotese
2015-10-05 20:56         ` Gregory Maxwell
2015-10-05 21:08           ` Tom Zander
2015-10-05 21:16             ` Milly Bitcoin
2015-10-05 21:26             ` Gregory Maxwell
2015-10-06  7:14               ` Tom Zander
2015-10-05 21:27             ` Peter R
2015-10-05 21:30               ` Gregory Maxwell
2015-10-05 21:36                 ` Milly Bitcoin
2015-10-05 21:37                 ` Peter R
2015-10-06  1:37           ` Tom Harding
2015-10-06  3:20             ` Peter R
2015-10-06  3:39               ` Milly Bitcoin
2015-10-06  4:54                 ` Luke Dashjr
2015-10-06  5:08                   ` Milly Bitcoin
2015-10-06  5:49                     ` Milly Bitcoin
2015-10-06  5:53                       ` Luke Dashjr
2015-10-06  6:03                         ` Milly Bitcoin
2015-10-06 22:14                       ` phm
2015-10-06  5:07               ` NotMike Hearn
2015-10-06  5:33                 ` Peter R
2015-10-05 19:36   ` Milly Bitcoin
2015-10-05 23:18 ` Eric Lombrozo
2015-10-06 17:28 ` Venzen Khaosan
2015-10-07  0:04   ` Sergio Demian Lerner

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=CAAS2fgSyWaRfXHKWZYzZ4X8ksMECaO47dTXum67XwpTTYnbDXg@mail.gmail.com \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=tomz@freedommail.ch \
    /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