From: Wladimir <laanwj@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin.org SOPA/PIPA blackout
Date: Mon, 16 Jan 2012 09:29:07 +0100 [thread overview]
Message-ID: <CA+s+GJBdQegz2=kDEbAmPw4wTVdduZhc2B+XnO49g6ZEXB8TKQ@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQYijky7g-K4dZF6x9NktnADuxRO6A=YAJxCF2gj85JHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On Mon, Jan 16, 2012 at 9:12 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> On Mon, Jan 16, 2012 at 2:35 AM, Wladimir <laanwj@gmail.com> wrote:
> > 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".
>
> Very few people actually care if they can load that particular URL ...
> if you were talking about the forums it might matter more. It also
> might make sense to run some informative popup, except people are
> going to be seeing them all over the internet on higher traffic sites.
>
Agreed, a notice would be enough. No need to make the entire site
inaccessible either.
Wladimir
[-- Attachment #2: Type: text/html, Size: 1054 bytes --]
next prev parent reply other threads:[~2012-01-16 8:29 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
2012-01-16 8:12 ` Gregory Maxwell
2012-01-16 8:29 ` Wladimir [this message]
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+GJBdQegz2=kDEbAmPw4wTVdduZhc2B+XnO49g6ZEXB8TKQ@mail.gmail.com' \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gmaxwell@gmail.com \
/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