From: sisadm101@clovermail•net
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Censorship
Date: Fri, 21 Aug 2015 13:03:33 -0500 [thread overview]
Message-ID: <20150821130333.Horde.9zPFmy3VMqAO5FGReDHaRg1@www.vfemail.net> (raw)
[-- Attachment #1: Plaintext Message --]
[-- Type: text/plain, Size: 1493 bytes --]
People are wondering why there is such a division in the bitcoin community
at this time. Bitcoin as a whole is only so big. The bitcoin discussion
communities are spread out, but there are only a few popular ones.
BitcoinTalk and Reddit seem to be the largest, most popular where bitcoin
discussion happens consistently and from almost everyone in the community
(devs, users, btc companies, merchants, and so on). I think we all know
where this is going. If not, here you go. BitcoinTalk and Reddit are
managed by a single person: Theymos. It's become quite clear over the past
several days/weeks, that Theymos is highly censoring bitcoin discussion,
mainly on Reddit, but also BitcoinTalk. If this single person is able to
censor content, and hush the debate, he (and whatever his agenda is), wins.
How can we as a community discuss these proposed changes, if the discussion
is from a one sided point of view? There doesn't seem to be a solution at
this time, but I find it dissapointing that many (in this very email list)
aren't discussing this important part of the issue. Maybe it's becuase
Theymos is anti-bigger blocks, which seems to coincide with the Blockstream
point of view, which many of the core devs belong to.
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
[-- Attachment #2: HTML Message --]
[-- Type: text/html, Size: 1936 bytes --]
next reply other threads:[~2015-08-21 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 18:03 sisadm101 [this message]
2015-08-22 13:39 ` David Vorick
2015-08-23 6:48 ` Jorge Timón
2015-08-31 6:43 ` hurricanewarn1
2015-08-31 8:45 ` NxtChg
2015-08-31 9:35 ` hurricanewarn1
2015-08-31 9:37 ` Btc Drak
2015-08-31 9:49 ` NxtChg
2015-08-31 10:25 ` Btc Drak
2015-08-31 10:38 ` NxtChg
2015-08-31 9:51 ` NxtChg
2015-08-31 11:46 ` Natanael
2015-08-31 12:06 ` hurricanewarn1
2015-08-31 10:33 ` Wladimir J. van der Laan
[not found] <CALGZhhvAV3iB=QDs2-NtLR5U7toqnygQAWU_ShPvL1xWX_upQQ@mail.gmail.com>
2015-08-31 17:00 ` hurricanewarn1
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=20150821130333.Horde.9zPFmy3VMqAO5FGReDHaRg1@www.vfemail.net \
--to=sisadm101@clovermail$(echo .)net \
--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