public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
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 16:36:48 -0400	[thread overview]
Message-ID: <55CFA2E0.9040301@bitcoins.info> (raw)
In-Reply-To: <CA+w+GKTG6a_v4Jop3FZ2O2WG9Fi=o0Lnh58OH4Y4sM-vPjFHSQ@mail.gmail.com>

> So if you want a user vote, that's an issue that'd have to be tackled:
> the people who admin the main communication channels Bitcoin users have
> vowed to censor any program that doesn't slavishly follow 51%+ hash
> power. That attempt to control the conversation is certainly not
> libertarian or democratic in nature, but there you go.

These types of actions are immediately apparent to anyone who looks at 
the Bitcoin ecosystem (Bitcoin.org, Githib, Wiki, bitcointalk, etc.) and 
were readily apparent long before any block size debate.  It is almost a 
taboo subject and anyone who raises these types of issues is immediately 
labeled as a "troll."  These are the people who used to run around 
saying that Bitcoin development is "decentralized" because anyone can 
fork the code and now many of the same people claim a fork will destroy 
everything.

The problem is that a small group of highly irrational and inexperienced 
people (outside of the small and unusual Bitcoin ecosystem) have control 
over the majority of the resources.  I think over time the problem will 
even itself out but currently it is an obstacle in moving Bitcoin forward.

Russ




  reply	other threads:[~2015-08-15 20:36 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-15 17:02 [bitcoin-dev] Bitcoin XT 0.11A 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 [this message]
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
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=55CFA2E0.9040301@bitcoins.info \
    --to=milly@bitcoins.info \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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