From: xor <xor@freenetproject•org>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Something people are forgetting about the Gentoo / Luke-jr censorship issue
Date: Fri, 10 Oct 2014 18:22:18 +0200 [thread overview]
Message-ID: <2262118.BDDGpkgqmz@1337h4x0r> (raw)
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
Hey folks,
FYI the issue is that Luke-Jr wants to include code which can censor stuff like
SatoshiDice transactions because he thinks they are denial of service:
https://bugs.gentoo.org/show_bug.cgi?id=524512
While everyone is jumping on the neutrality Bitcoin should have, you're
forgetting that there are also *legal* implications:
The *technical ability'* to filter certain types of network traffic can cause you
to be legally liable to *USE* it to filter illegal stuff.
So even if the filter code is disabled by default, it can put Bitcoin users in
legal danger: Law enforcement can try to force them to use it.
This for sure depends on the country you are living in, but in general I think
it can be agreed that it will be a lot easier to defend a "my node relays
everything uncensored" policy against law enforcement if you wouldn't even
have the technical ability to filter stuff because the code just cannot do it
anyway.
So please do not even include this code as disabled, and if possible do not
even write or publish it :)
Also, as I don't have a Gentoo bugtracker account, can someone please add this
comment there?
Thanks & Gretings,
xor - a developer of https://freenetproject.org/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-10-10 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 16:22 xor [this message]
2014-10-10 16:42 ` Jeff Garzik
2014-10-10 17:26 ` Mike Hearn
2014-10-10 18:41 ` Justus Ranvier
2014-10-10 19:02 ` Thomas Zander
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=2262118.BDDGpkgqmz@1337h4x0r \
--to=xor@freenetproject$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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