public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Jorge Timón" <jtimon@jtimon•cc>
To: David Vorick <david.vorick@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Censorship
Date: Sun, 23 Aug 2015 08:48:38 +0200	[thread overview]
Message-ID: <CABm2gDpEFdG=JAO2owTZOEae22qwfgjiedHC0-tL9oGCO1=CFw@mail.gmail.com> (raw)
In-Reply-To: <CAFVRnypEF+bkpxkoQOdMzK9PdDAJ5GieOyUtY=0_72SBuGBPvQ@mail.gmail.com>

This is off-topic here.
Consensus critical changes (those aren't changes that Bitcoin Core
developers can make unilaterally against the will of alternative
implementations or users) and Bitcoin Core development are independent
from bitcointalk.org and /r/bitcoin.
And as you say, people can create competing without moderation or
"censorship" (ie /r/bitcoin_uncensored or bitcontalkuncensred.org
/r/bitcoin_moderated_by_someone_else ).


On Sat, Aug 22, 2015 at 3:39 PM, David Vorick via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>


  reply	other threads:[~2015-08-23  6:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 18:03 sisadm101
2015-08-22 13:39 ` David Vorick
2015-08-23  6:48   ` Jorge Timón [this message]
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='CABm2gDpEFdG=JAO2owTZOEae22qwfgjiedHC0-tL9oGCO1=CFw@mail.gmail.com' \
    --to=jtimon@jtimon$(echo .)cc \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=david.vorick@gmail$(echo .)com \
    /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