[ai-control] Re: Considerations for AI Opt-Out

Mark Nottingham <mnot@mnot.net> Sat, 18 May 2024 03:22 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: ai-control@ietfa.amsl.com
Delivered-To: ai-control@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEF93C151068 for <ai-control@ietfa.amsl.com>; Fri, 17 May 2024 20:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="PmDXUcNE"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="SKzR/g+A"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B7yuKZHOdqTx for <ai-control@ietfa.amsl.com>; Fri, 17 May 2024 20:22:04 -0700 (PDT)
Received: from wfout1-smtp.messagingengine.com (wfout1-smtp.messagingengine.com [64.147.123.144]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDB89C14F6E4 for <ai-control@ietf.org>; Fri, 17 May 2024 20:22:04 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.west.internal (Postfix) with ESMTP id 5C16E1C000DA; Fri, 17 May 2024 23:22:02 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 17 May 2024 23:22:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1716002522; x=1716088922; bh=j9oDwWgehFmHNppHzjXF7xqcJymEy8sIr2X43a96ATs=; b= PmDXUcNE3ru0C1XdNX90Qd2m0PLArjP3ykVAdE4rMUIV1OkgZ0pvYrWJw5FW5erX yI5lLVGMzvB9/zei5jqRfeyRJ66jxaBDLwWKGPhv+WWSY7cV6RYd7JBIILCQqB/B yszOVpPEB8WlAfKd+YGQKcky+0Mw0tkfz6PPrJ5WPWXPskxJ8UKZWMYJMpk+MHke x2hfYFBxj2XGl2e19jCUnsaJR32Vk77HccNcN6fGBB/loBqNnnnoLPJVMC3vZU93 ZThIhnyD3+8JpKQrbv7jWDiyLzRooTzWfv+3Zzvf4N+TzjSPJWRKBFsDM8I61qse nUjN+swvfXNAJg6ND99QCA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1716002522; x= 1716088922; bh=j9oDwWgehFmHNppHzjXF7xqcJymEy8sIr2X43a96ATs=; b=S KzR/g+AicxYhqVo3EbIu4dB1ScIuzDBf+sYxo117/eDr9Oq9ohH08XxNFLxZoncJ A7vlcvXcY7ZsUoAuoKH0jD0Kwk/DBE1agYv9DDOl4am1nZGHR9L6ZDHgDYNm4PLG LucnZT1ITAvaSRN8DpjE0BV9s1Z5tC5wQyj3l66a+Nk99ezRqa+NEDwqIYhiA0Ox pwlE2432pVs/BBqJu0B2W7YL2Zn3dPGtNDRvNspFBiiEq52s/5ZV4RJylG5m9iJp qthGn53tzksivHzl3wXnNcdKfdITGWL5WePygUgL4OtrbP4YO/UDjXGWiToWa8iq Z615oYx+r+tdBCMpD7kUQ==
X-ME-Sender: <xms:2R5IZjGrS9lcHlqQUoWjKp2iPvoHFflBQ8IGedW2RW0PeO8JhbIu6Q> <xme:2R5IZgUGKBgyvbMDrMz-GJr3WyWsmTXquEfgHWPlZqgHnspKRH5ivWP0delYS0nvV FTAhYVj2MY-Hz89yg>
X-ME-Received: <xmr:2R5IZlJmbxiYZRxjhIkexiS1dsrJCt6h3fSsOJrJoZsCdaTPVuuSZPotOuvOcEjhDOp-LDVzduCRdbqwmvbpntFJ44lhBZMzrqawfcCuveortgcCgElTTSGu>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdehhedgieekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjffevgffkfhfvofesth hqmhdthhdtjeenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnhhothes mhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeffgeduhfdtteetfeeiheeggfduvd ekuddtuedtudeiieetffefveffieegtdetffenucffohhmrghinheprghrshhtvggthhhn ihgtrgdrtghomhdpmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:2R5IZhGp1zE1WAPoLDMvpPWgXp9gIDxUi2acCV9JIgCNkb781tsMwA> <xmx:2R5IZpUGqNAU6fgtQk4mCMZ1caYusT5OwfJJx8OsqjVfn9Y2htPTeA> <xmx:2R5IZsNHt5UCqWB6kHVqjgC0e2f5PVTJidObbcm-9UL7BNwWAlyppA> <xmx:2R5IZo1R5B23f8ieTuSUS9mOmZrHCRydfQhicVwRf3BE3bn-jpFLNA> <xmx:2R5IZsTCCYQ8LYt83n6n6E5zTMbjj_AfzQRKb9v4cAPZsOPe9SHUIH5U>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 17 May 2024 23:22:00 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <AM5PR01MB299431A3FBD50BD1F64E64F6A8EE2@AM5PR01MB2994.eurprd01.prod.exchangelabs.com>
Date: Sat, 18 May 2024 13:21:56 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C9CA076-63D2-4E82-A13B-A02C6921B5F0@mnot.net>
References: <66D05E57-6474-414D-AF4C-409B063E970F@mnot.net> <AM5PR01MB299431A3FBD50BD1F64E64F6A8EE2@AM5PR01MB2994.eurprd01.prod.exchangelabs.com>
To: Chris Needham <chris.needham=40bbc.co.uk@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: H2YRLFOYICDZR22SSVVYZPQPVPLBT7U5
X-Message-ID-Hash: H2YRLFOYICDZR22SSVVYZPQPVPLBT7U5
X-MailFrom: mnot@mnot.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "ai-control@ietf.org" <ai-control@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [ai-control] Re: Considerations for AI Opt-Out
List-Id: AI Control <ai-control.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ai-control/TKaTOuM6gu6KpvGiPL7uS1HLAbY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ai-control>
List-Help: <mailto:ai-control-request@ietf.org?subject=help>
List-Owner: <mailto:ai-control-owner@ietf.org>
List-Post: <mailto:ai-control@ietf.org>
List-Subscribe: <mailto:ai-control-join@ietf.org>
List-Unsubscribe: <mailto:ai-control-leave@ietf.org>

Hi Chris,

> On 18 May 2024, at 12:31 AM, Chris Needham <chris.needham=40bbc.co.uk@dmarc.ietf.org> wrote:
[...]
> There needs to be a solution for a global opt-out like this, and I'd suggest also more fine grained controls for particular "AI" use cases like generative AI training LLMs, detection and classification, or possibly for allowing some crawlers and not others.

Yes! Part of the problem here is that AI is still evolving rapidly, so techniques and applications may emerge that test the assumptions of any framework established. 

At the same time, we should be wary of a framework that's so detailed that it creates friction against adoption (e.g., P3P), or one that's so extensible that it can be subverted by powerful implementers (e.g., SOAP).

> For specs like IPTC and CAWG's that embed the opt-outs in image or video assets, when content is voluntarily uploaded to such sites (rather than being scraped by them), would the social site's T&Cs apply, overriding any assertions in the content itself?

Good question. I suspect precedence needs to be specified, or each site will decide however is most advantageously to it. That might mean the most restrictive policy available always wins.

It also hints at another issue -- content on platforms that intermediate and control, like what is being seen now on StackOverflow and Slack:
  https://arstechnica.com/tech-policy/2024/05/slack-defends-default-opt-in-for-ai-training-on-chats-amid-user-outrage/

In other words, easy content creation tools that live within walled gardens controlled by platforms whose interests often don't always align with those of their users. 

That content is often textual (which isn't amenable to embedded policy), and/or lives entirely within the platform, which can choose what affordances for expressing preferences are available to users (with attendant dark patterns).

My initial thought is that technical controls aren't really effective in these situations; they require policy intervention and oversight (because of the likelihood of dark patterns being used to steer users' actions). That said, we should consider how those cases might interact with technical controls.

Cheers,

--
Mark Nottingham   https://www.mnot.net/