Re: [Trans] Putting illegal stuff in an append only ledger

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Wed, 21 March 2018 09:46 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B347120726 for <trans@ietfa.amsl.com>; Wed, 21 Mar 2018 02:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCgfVgTkO5rw for <trans@ietfa.amsl.com>; Wed, 21 Mar 2018 02:46:47 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E5B312D963 for <trans@ietf.org>; Wed, 21 Mar 2018 02:46:47 -0700 (PDT)
Received: from fifthhorseman.net (dhcp-8362.meeting.ietf.org [31.133.131.98]) by che.mayfirst.org (Postfix) with ESMTPSA id B2CADF99A; Wed, 21 Mar 2018 05:46:45 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 1F96920572; Wed, 21 Mar 2018 09:46:42 +0000 (GMT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Tao Effect <contact@taoeffect.com>, Paul Wouters <paul@nohats.ca>
Cc: trans@ietf.org
In-Reply-To: <A8C94DE7-537D-4455-97A6-65E54D537D0B@taoeffect.com>
References: <C7855D7B-E853-443F-9C7E-4C901216CDFB@nohats.ca> <A8C94DE7-537D-4455-97A6-65E54D537D0B@taoeffect.com>
Date: Wed, 21 Mar 2018 09:46:41 +0000
Message-ID: <87k1u5sqv2.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/f-kxfgp3prVjDbyqg9aZFdQcXNE>
Subject: Re: [Trans] Putting illegal stuff in an append only ledger
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 09:46:50 -0000

On Tue 2018-03-20 19:12:04 -0400, Tao Effect wrote:
> I don't think it's a real problem, just another week, another social
> attack on Bitcoin from those who are heavily invested in seeing
> Bitcoin die.
>
> The reason why it's not a legitimate issue are here:
>
> https://lobste.rs/s/walhsk/child_abuse_imagery_found_within_bitcoin#c_xf6oor
>
> And here:
>
> https://lobste.rs/s/walhsk/child_abuse_imagery_found_within_bitcoin#c_76hm8v
>
> But that will not stop people from pretending it is.

IIUC, the webforum comments that these links point to argue that because
there is work required outside the blockchain to assemble the toxic
data, the data in question doesn't *just* reside in the blockchain.  Is
that right, or do you have another interpretation?

I don't see how it follows from this particular situation that there
would be no way to put toxic data in the global append-only ledger that
Bitcoin depends on.  Do you think that there is some principled reason
why the blockchain can avoid ingestion of toxic data of any form,
whether it's (depending on your jurisdiction) CP or "intellectual
property" or blasphemy or hate speech or …?

Does your argument for why the bitcoin blockchain is defended against
this hold for arbitrary global append-only datastructures, or is it
specific to bitcoin?

Regards,

          --dkg