From: slush <slush@centrum.cz>
To: Alan Reiner <etotheipi@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin.org SOPA/PIPA blackout
Date: Tue, 17 Jan 2012 01:59:25 +0100 [thread overview]
Message-ID: <CAJna-HjMSvnJxXnnvC_mGEsHNX=7yaDU3W22P8LwbbbuX2dEvQ@mail.gmail.com> (raw)
In-Reply-To: <4F14C4EF.5070709@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4027 bytes --]
> I agree Bitcoin should avoid making any bold political stands.
I agree on this. Please don't turn Bitcoin project/homepage into some
political agitation. Not everybody care about political attitude of main
project developers.
slush
On Tue, Jan 17, 2012 at 1:46 AM, Alan Reiner <etotheipi@gmail.com> wrote:
> **
> You guys are representing both extremes of the issue. In response to Jeff
> and Luke-Jr, I don't see how this is *just any other poltical issue*. It
> strikes at the heart of everything Bitcoin is about. Barring
> Bitcoin-specific legislation, I don't see how any legislation could be more
> relevant to Bitcoin and the community around it.
>
> On the other hand, Bitcoin is still a non-entity, and shouldn't get in the
> business of making statements. A central voice for Bitcoin gives the
> impression that it is actually centralized, and one that has opinions.
> Plus I wouldn't be surprised if some, heavily-invested Bitcoin users were
> of the opinion that SOPA/PIPA/whatever could be a huge profit for
> themselves: once SOPA kicks in and businesses around the world start
> getting cut off for legit or illegitimate purposes, a lot of them could
> potentially switch to Bitcoin to keep their business going. That could be
> a huge boon for Bitcoin. You may not agree it's worth the tradeoff, but
> people are selfish and may not actually understand or even care about SOPA
> legislation itself.
>
> I think it's *not inappropriate* for something to be mentioned on the
> website about Bitcoin's philosophy being threatened by SOPA, but I agree
> Bitcoin should avoid making any bold political stands. Users could be
> reminded that SOPA affects yet another thing they care about, but it might
> be better to avoid it altogether. If any response is made, it should be a
> very light one.
>
> -Alan
>
>
>
> On 01/16/2012 07:30 PM, Amir Taaki wrote:
>
> Bunk argument. This is an issue that affects bitcoin directly.
>
> Wikipedia has far more need to remain neutral and apolitical than bitcoin ever does- you've read Satoshi's politically charged whitepaper or seen the genesis block quote.
> http://en.wikipedia.org/wiki/Wikipedia:SOPA_initiative/Action
>
> The Wikipedia community decided on a full and global blackout. Bitcoin should do the same in unison with the rest of the web- sites like Reddit, 4chan and Wikipedia.
>
> It's funny / almost comical how you consign this to being just another issue or case of moral alarm. Sad.
>
>
>
> ----- Original Message -----
> From: Jeff Garzik <jgarzik@exmulti.com> <jgarzik@exmulti.com>
> To: Amir Taaki <zgenjix@yahoo.com> <zgenjix@yahoo.com>
> Cc: "bitcoin-development@lists.sourceforge.net" <bitcoin-development@lists.sourceforge.net> <bitcoin-development@lists.sourceforge.net> <bitcoin-development@lists.sourceforge.net>
> Sent: Sunday, January 15, 2012 10:37 PM
> Subject: Re: [Bitcoin-development] bitcoin.org SOPA/PIPA blackout
>
> On Sun, Jan 15, 2012 at 5:09 PM, Amir Taaki <zgenjix@yahoo.com> <zgenjix@yahoo.com> wrote:
>
> How is this not the most important world issue right now?
>
> EVERYTHING is under threat. Go nuclear to show our nerd-rage.
>
> Everybody blank your personal sites too. Americans, take to the streets. World, go scream at the US embassy.
>
> 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.
>
>
>
>
>
> ------------------------------------------------------------------------------
> 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: 5457 bytes --]
next prev parent reply other threads:[~2012-01-17 1:28 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
2012-01-17 0:30 ` Amir Taaki
2012-01-17 0:46 ` Alan Reiner
2012-01-17 0:59 ` slush [this message]
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='CAJna-HjMSvnJxXnnvC_mGEsHNX=7yaDU3W22P8LwbbbuX2dEvQ@mail.gmail.com' \
--to=slush@centrum.cz \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=etotheipi@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