public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: David Vorick <david.vorick@gmail.com>
To: sisadm101@clovermail.net
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Censorship
Date: Sat, 22 Aug 2015 09:39:13 -0400	[thread overview]
Message-ID: <CAFVRnypEF+bkpxkoQOdMzK9PdDAJ5GieOyUtY=0_72SBuGBPvQ@mail.gmail.com> (raw)
In-Reply-To: <20150821130333.Horde.9zPFmy3VMqAO5FGReDHaRg1@www.vfemail.net>

[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]

I am not sure that this is on-topic for the bitcoin-dev mailing list, but
it seems politically relevant enough that I'm going to respond.

/r/bitcoin and bitcointalk.org are both discussion websites that pertain to
a specific topic. All (or nearly all) discussion websites pertaining to a
specific topic have a set of rules that get enforced to facilitate relevant
and interesting discussion. These rules help to block spam, and help to
make sure that discussions happen in their appropriate places. The rules in
place on the two primary bitcoin discussion sites have helped facilitate a
large userbase frequented by many relevant experts. I do believe that we
can thank the strict moderation policies for much of the activity that
happens which is technically interesting.

/r/bitcoin and bitcointalk.org are both centralized forums. As such, the
rules are going to be set by a centralized authority. The rules set have
been set to keep the discussion as interesting and relevant as possible.
When a certain theme becomes a massive echo chamber or little more than
beating a dead horse, it makes sense to implement moderation. Calling it
'censorship' is misleading, because a government authority is not
threatening punishment for the discussion of a certain topic. People are
not banned from visiting forums or websites where off-topic (or
against-the-rules) discussion is happening. People's /r/bitcoin rights are
not being revoked because they are subscribed to a controvertial subreddit.
That would be censorship.

Many people are clearly unhappy with the moderation happening on /r/bitcoin
and bitcointalk.org. Luckily, the switching cost for online discussion
forums is very low. I'm now going to invite people to post links to bitcoin
discussion forums where the moderation authority is different.

I know that a recently popular subreddit is /r/bitcoin_uncensored

I am interested to see what other forums people think are worth mentioning.

[-- Attachment #2: Type: text/html, Size: 2214 bytes --]

  reply	other threads:[~2015-08-22 13:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 18:03 [bitcoin-dev] Censorship sisadm101
2015-08-22 13:39 ` David Vorick [this message]
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='CAFVRnypEF+bkpxkoQOdMzK9PdDAJ5GieOyUtY=0_72SBuGBPvQ@mail.gmail.com' \
    --to=david.vorick@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=sisadm101@clovermail.net \
    /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