public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Wladimir J. van der Laan" <laanwj@gmail•com>
To: sisadm101@clovermail•net
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Censorship
Date: Mon, 31 Aug 2015 12:33:21 +0200	[thread overview]
Message-ID: <20150831103319.GA27605@amethyst.visucore.com> (raw)
In-Reply-To: <20150821130333.Horde.9zPFmy3VMqAO5FGReDHaRg1@www.vfemail.net>


On Fri, Aug 21, 2015 at 01:03:33PM -0500, sisadm101--- via bitcoin-dev wrote:
> 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)

Please, this has drifted so far from the goal of this list: bitcoin development, and technical and academic debate about that.

Meta-discussion of communities has no place here.

I'd say: in the spirit of permissionlessness, everyone can create a community or list about bitcoin. If you don't agree with the admin, create your own. That's more constructive use of everyone's time and energy than trying to pressure people to change their behavior on their own home turf.

Wladimir


  parent reply	other threads:[~2015-08-31 10:33 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
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 [this message]
     [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=20150831103319.GA27605@amethyst.visucore.com \
    --to=laanwj@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=sisadm101@clovermail$(echo .)net \
    /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