From: Milly Bitcoin <milly@bitcoins•info>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin XT 0.11A
Date: Sat, 15 Aug 2015 20:06:44 -0400 [thread overview]
Message-ID: <55CFD414.4080702@bitcoins.info> (raw)
In-Reply-To: <CAOG=w-uTd_V5usB79sLc8E_3R2oxmYqriO6XnrRVcz3Gw7NHuw@mail.gmail.com>
> Baseless accusations also have no place on this mailing list. They are
> unprofessional, and poisonous to the consensus-building process we all
> seek to engage in.
I didn't see any baseless accusations in the message. I saw a
discussion of possible conflicts of interest. Your reply seems to
indicate that somehow conflicts of interest don't exist with the
developers or that the developers are somehow above everyone else. The
fact is the developers on this list discuss conflicts of interest all
the time as it relates to things like mining. Conflicts of interest are
going to be a regular part of Bitcoin development so you should start
getting used it because it is only going to increase as the value increases.
It is your messages attacking people who raise legitimate issues that is
poisonous. It tries to prevent discussions of the risks associated with
the code development. It creates an atmosphere where people are
blackballed if they discuss these issues. This is what happens in
religions all the time and it is time to start treating Bitcoin like the
technology that it is rather than some cult religion.
For all I know is that a hard fork controversy is going to cause the
price to drop temporarily so for all I know this is a scheme to buy some
cheap coins just like when hackers used to attack exchanges and
bitcointalk at the same time to get the price to drop. (I don't think
it is a scheme to do that but such a scheme is certainly possible in the
future and things like that should be expected to happen).
Russ
next prev parent reply other threads:[~2015-08-16 0:06 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 17:02 Mike Hearn
2015-08-15 17:57 ` s7r
2015-08-15 18:38 ` s7r
2015-08-15 19:21 ` Mike Hearn
2015-08-15 20:36 ` Milly Bitcoin
2015-08-15 20:47 ` Bryan Bishop
2015-08-15 21:10 ` Milly Bitcoin
2015-08-15 20:55 ` Micha Bailey
2015-08-15 21:32 ` Eric Lombrozo
2015-08-15 22:01 ` Ken Friece
2015-08-15 22:16 ` Eric Lombrozo
2015-08-15 22:27 ` Angel Leon
2015-08-15 22:28 ` Ken Friece
2015-08-15 22:55 ` Mark Friedenbach
2015-08-15 23:04 ` Ken Friece
2015-08-15 23:07 ` Eric Lombrozo
2015-08-15 23:30 ` Michael Naber
2015-08-15 23:40 ` Mark Friedenbach
2015-08-15 23:57 ` Ken Friece
2015-08-16 0:06 ` Milly Bitcoin [this message]
2015-08-16 13:49 ` Mike Hearn
2015-08-16 15:44 ` Anthony Towns
2015-08-16 16:07 ` Tamas Blummer
2015-08-16 16:12 ` Levin Keller
2015-08-16 17:01 ` Adam Back
2015-08-16 18:15 ` Tamas Blummer
2015-08-16 20:27 ` Eric Voskuil
2015-08-15 22:39 muyuubyou
2015-08-16 18:37 ` Andrew LeCody
2015-08-16 23:02 ` Cameron Garnham
2015-08-16 23:22 ` Andrew LeCody
2015-08-17 0:03 ` Cameron Garnham
2015-08-17 6:42 ` Peter Todd
2015-08-17 12:29 ` Andrew LeCody
2015-08-17 12:33 ` Eric Lombrozo
2015-08-19 10:09 ` Jorge Timón
2015-08-19 15:41 ` s7r
2015-08-19 22:28 ` Jorge Timón
2015-08-19 22:45 ` Adam Back
2015-08-19 23:23 ` Peter Todd
2015-08-20 10:25 ` s7r
2015-08-20 11:32 ` Milly Bitcoin
2015-08-20 11:46 ` Hector Chu
2015-08-20 12:29 ` Milly Bitcoin
2015-08-20 14:25 ` Tamas Blummer
2015-08-17 21:42 ` Matt Corallo
2015-08-16 2:08 muyuubyou
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=55CFD414.4080702@bitcoins.info \
--to=milly@bitcoins$(echo .)info \
--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