public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin.org SOPA/PIPA blackout
Date: Mon, 16 Jan 2012 08:35:30 +0100	[thread overview]
Message-ID: <CA+s+GJA6vq=9FQw4aHYv0x9xY2E1nenMjzL+vgwCxFWcJM8dZg@mail.gmail.com> (raw)
In-Reply-To: <201201152019.36066.luke@dashjr.org>

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

Internet censorship *is* a threat to bitcoin, if we don't stand up for our
rights now we deserve anything that is coming. There will be no "long run".

On Mon, Jan 16, 2012 at 2:19 AM, Luke-Jr <luke@dashjr.org> wrote:

> On Sunday, January 15, 2012 5:37:05 PM Jeff Garzik wrote:
> > There are always issues that raise ire and moral outrage.  I would
> > rather that bitcoin.org stay apolitical -- our users will appreciate
> > this in the long run.
>
> I agree (with the conclusion). There are much more important and urgent
> problems than SOPA/PIPA that we'd need to constantly 'blackout' if we did
> it
> over every single problem.
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Mar 27 - Feb 2
> Save $400 by Jan. 27
> Register now!
> http://p.sf.net/sfu/rsa-sfdev2dev2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

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

  reply	other threads:[~2012-01-16  7:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15 22:09 [Bitcoin-development] bitcoin.org SOPA/PIPA blackout Amir Taaki
2012-01-15 22:37 ` Jeff Garzik
2012-01-16  1:19   ` Luke-Jr
2012-01-16  7:35     ` Wladimir [this message]
2012-01-16  8:12       ` Gregory Maxwell
2012-01-16  8:29         ` Wladimir
2012-01-17  0:30   ` Amir Taaki
2012-01-17  0:46     ` Alan Reiner
2012-01-17  0:59       ` slush
2012-01-17  2:35         ` Cameron Garnham
2012-01-17  2:25       ` Luke-Jr
2012-01-17  9:19     ` Vladimir Marchenko
2012-01-17  2:37   ` Kyle Henderson
2012-01-17  6:15     ` Gregory Maxwell
2012-01-17  7:42       ` Jorge Timón
2012-01-17  9:04         ` Wladimir
2012-01-17 16:03         ` Luke-Jr
2012-01-17 16:16           ` James Burkle
2012-01-17 16:30             ` solar
2012-01-17  9:25       ` Stefan Thomas
2012-01-17 19:03 Peter Vessenes

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='CA+s+GJA6vq=9FQw4aHYv0x9xY2E1nenMjzL+vgwCxFWcJM8dZg@mail.gmail.com' \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=luke@dashjr.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