From: Wladimir <laanwj@gmail•com>
To: "Jorge Timón" <timon.elviejo@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin.org SOPA/PIPA blackout
Date: Tue, 17 Jan 2012 10:04:22 +0100 [thread overview]
Message-ID: <CA+s+GJBqAPmcwD0Z7AyQsPZgxfyNnU+OoOcE39N8XCk2ZEOm9Q@mail.gmail.com> (raw)
In-Reply-To: <CAGQP0AFyASUwgpgyWJobq1WypRjP9NuXSF2bPfrB8dX_xYti-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
This is not just "a political issue". The internet as we know it is at
stake, and bitcoin depends directly on a working, single, globally
connected internet (at least for now, until mesh networking goes
anywhere...).
*Everyone* using bitcoin has the interest in keeping the internet working
and un-balkanized. That's not a political opinion, it's a fact.
The laws could also criminalize both the users and developers, if they
regard bitcoin as a "payment network". And countries aren't too fussy about
extradition to the US (see the case of Richard O'Dwyer).
Though I agree that SOPA and PIPA are just manifestations of a brand of
censorship that is spreading all over the world. Stopping these laws won't
solve the underlying issue either. Other countries will keep pushing for
them, and we can't blank out the page for every country.
However, that does not make the issue "political and thus meaningless".
Also: "being too small to matter" is never a good argument to not do
something. It is fear paralysis.
Wladimir
2012/1/17 Jorge Timón <timon.elviejo@gmail•com>
> It may be a political issue, but I don't think wikipedia becomes a
> political organization for being against censorship.
> This is not about left or right. Is about free speech, one of the
> basic principles not only of freedom but also of democracy.
> And as Gregory shows it clearly affects bitcoin directly.
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2782 bytes --]
next prev parent reply other threads:[~2012-01-17 9:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 22:09 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
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 [this message]
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+GJBqAPmcwD0Z7AyQsPZgxfyNnU+OoOcE39N8XCk2ZEOm9Q@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=timon.elviejo@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