public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "NxtChg" <nxtchg@hush.com>
To: "Eric Lombrozo" <elombrozo@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Annoucing Not-BitcoinXT
Date: Mon, 17 Aug 2015 18:10:47 +0300	[thread overview]
Message-ID: <20150817151047.36D9943112@smtp.hushmail.com> (raw)
In-Reply-To: <64C86292-6671-4729-8A77-63C081797F62@gmail.com>

Eric,

>In the entire history of Bitcoin we've never attempted anything even closely resembling a hard fork like what's being proposed here.

These concerns are understandable. What's hard to understand is why he, he and he get to decide what is more risky - hitting the limit or forking for larger blocks?

Many people don't seem to think the upcoming hard fork is such a big risk.

---

And why there's so much fear that your side might lose to XT in a honest battle? Why is it suddenly not "let the best man win", but "we are right, they are enemies of the state, go get them!!!"?

This is the same fear dictators have of honest elections. If you know you can't win in a honest battle, you start rigging the game.

With recent "Satoshi" post even this list is not immune...

----

I don't know if everybody had a chance to appreciate this quote by theymos yet:

"If 90% of /r/Bitcoin users find these policies to be intolerable, then I want these 90% of /r/Bitcoin users to leave."

(https://www.reddit.com/r/Bitcoin/comments/3h9cq4/its_time_for_a_break_about_the_recent_mess/)

This is a quote worthy of Gaddafi. Fortunately, it's hard to be a dictator on the Internet, where you can't shoot people.



  parent reply	other threads:[~2015-08-17 15:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16 22:34 [bitcoin-dev] Annoucing Not-BitcoinXT jyellen
2015-08-17  3:10 ` jl2012
2015-08-17  7:04 ` Peter Todd
2015-08-17 10:09 ` NxtChg
2015-08-17 12:40   ` Vali Zero
2015-08-17 13:34     ` NxtChg
2015-08-17 14:03       ` Eric Lombrozo
2015-08-17 14:09         ` Levin Keller
2015-08-17 14:30           ` Eric Lombrozo
2015-08-17 14:36         ` Adam Back
2015-08-17 14:58           ` GC
2015-08-17 15:03           ` Levin Keller
2015-08-17 15:07             ` Eric Lombrozo
2015-08-19  3:49           ` odinn
2015-08-17 15:10         ` NxtChg [this message]
2015-08-17 16:37       ` Eric Lombrozo
2015-08-17 16:55         ` Eric Lombrozo
2015-08-18  4:37           ` Dave Scotese
2015-08-18  5:13             ` GC
2015-08-18  5:33               ` Dave Scotese
2015-08-18  9:46         ` NxtChg
2015-08-19  9:47           ` Jorge Timón

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=20150817151047.36D9943112@smtp.hushmail.com \
    --to=nxtchg@hush.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=elombrozo@gmail.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