From: Peter Vessenes <peter@coinlab.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin.org SOPA/PIPA blackout
Date: Tue, 17 Jan 2012 11:03:36 -0800 [thread overview]
Message-ID: <CAMGNxUu5Owk0w2THhPfLj1_Uo1V=FSuzS=NS1HqYdek1rrZz6Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
It seems to me that the internet as a whole has got this one covered. I say
this as someone who thinks that BitCoin needs to choose its battles and
craft its reputation extremely carefully; this isn't the most important
fight for BitCoin, nor the most deadly.
I do think SOPA and PIPA could impact bitcoin, what if, for instance,
copyrighted material made its way into the blockchain?
Already the DMCA would make it hard for someone publishing blocks online to
do anything but cease under a DMCA request. SOPA, at least, would go
farther and allow the US to cut all access to 'offending' sites elsewhere
in the world.
At any rate, I don't think these bills are 'aimed at' BitCoin, and the
companies with the most stake are taking the threat quite seriously.
[-- Attachment #2: Type: text/html, Size: 863 bytes --]
next reply other threads:[~2012-01-17 19:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 19:03 Peter Vessenes [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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='CAMGNxUu5Owk0w2THhPfLj1_Uo1V=FSuzS=NS1HqYdek1rrZz6Q@mail.gmail.com' \
--to=peter@coinlab.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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