[ai-control] prevent robots.txt entries from becoming law

Brewster Kahle <brewster@archive.org> Fri, 18 July 2025 18:56 UTC

Return-Path: <brewster@archive.org>
X-Original-To: ai-control@mail2.ietf.org
Delivered-To: ai-control@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id C1CF645C2D89 for <ai-control@mail2.ietf.org>; Fri, 18 Jul 2025 11:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.295
X-Spam-Level:
X-Spam-Status: No, score=-2.295 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, URIBL_SBL_A=0.1] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=archive.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kZrGWW67GNFZ for <ai-control@mail2.ietf.org>; Fri, 18 Jul 2025 11:56:55 -0700 (PDT)
Received: from mail.archive.org (mail.archive.org [207.241.224.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2C9BE45C2D82 for <ai-control@ietf.org>; Fri, 18 Jul 2025 11:56:55 -0700 (PDT)
Received: from mail.archive.org (localhost [127.0.0.1]) by mail.archive.org (Postfix) with ESMTP id 63C1350E7F for <ai-control@ietf.org>; Fri, 18 Jul 2025 18:56:54 +0000 (UTC)
Received: from smtpclient.apple (vpn-router-200p.us.archive.org [207.241.239.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: brewster@archive.org) by mail.archive.org (Postfix) with ESMTPSA id 465524FC9B for <ai-control@ietf.org>; Fri, 18 Jul 2025 18:56:54 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=archive.org; s=s2024; t=1752865014; bh=EejAi8oSsFCO+PYxSyKBWiIlBduxYCzmGHdDAW8Ztc4=; h=From:Subject:Date:To:From; b=LMstp03zLs2r/RG/8Qn4V29QQrpPbmp+cWg0W+vQx20NSjVgmj1ed49KtGq2wi5nu yyHOVwv1iXQ7uRVpbACoKgIZYci6qdknUV+VSm7EyDP9HmykrLD7xE3revtJP4iQho 4aqrcvj4/6lKNwHo5TmkDYrr73sm1ytRbIdYs09U7C9swLg36ERmPk7n0dWqyJ6vvR uBwmKi10XsqWjoOtttFXwH4tfkdy4ippFhVNVf93XKyPDyeYYIj2ZPvYvmVfrE0Ryo Yr5/qDB6kdbud0ur1RO1i3kwH32QVsZvh+8Ou0L1vSqcIyXqDhD/BK8FLzFO0QxY5z 26KljzC9gQbRw==
From: Brewster Kahle <brewster@archive.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_49A69168-3AE9-4AB5-A658-7E7C80473FB2"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Message-Id: <CF4FA93F-3BCA-4E64-8BE3-6E86ABE824CA@archive.org>
Date: Fri, 18 Jul 2025 11:56:43 -0700
To: ai-control@ietf.org
X-Mailer: Apple Mail (2.3826.600.51.1.1)
X-Envelope-From: <brewster@archive.org>
Message-ID-Hash: TIWLFY46MHXMQKBDUCWOCBFFECTXY2TD
X-Message-ID-Hash: TIWLFY46MHXMQKBDUCWOCBFFECTXY2TD
X-MailFrom: brewster@archive.org
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [ai-control] prevent robots.txt entries from becoming law
List-Id: AI Control <ai-control.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ai-control/iy38WylitCEjq76ZogVLcriHeOQ>
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>


Putting publishers online in the early 90’s at WAIS Inc and then running the Internet Archive, I was involved when robots.txt started, and have had to deal with it for 30 years.   Yes, there are issues around AI, but let’s not lose some basic principles of IETF now.  Sorry to chime in late, but it is important.

The proposal to insert AI language hijacks robots.txt and twists it into a tool for monetizing the internet. It also invites people to add it into laws (EU seems moving there). We successfully fought off efforts for decades (yes, there were those wanting to make robots.txt into law in the US).

The only way around this is to not add in the AI components into the standard, and let anyone voluntarily use it as they will (already happening).

To be more specific:

Robots.txt seemed like a great thing in 1994.  Keep robots from inadvertently moving cameras in coffee-pot watching websites, modifying mailing lists, etc.  It worked for a while as a voluntary system, but as time went along it did not even reflect the policies of the websites.   Then we got compound websites (think geocities and facebook etc) and robots.txt gives inappropriate power for the platforms.  

Often robots.txt files are put in place by a technical person in response to a temporary technical issue, then never rescinded.  For instance, I talked repeatedly with a deputy librarian of congress about a robot exclusion on a subsite of public domain materials that had been placed on the LOC.gov <http://loc.gov/> website.  This was not the policy of the Library of Congress. He could not, in practice, get it removed from the LOC website, no matter how he tried.   This is replicated over and over across the web, making robots.txt a less effective tool over time.   Making it a matter of law would not serve website owners well, legitimate crawlers well, and certainly not users of the WWW.

Having anything in robots.txt reflected in law is such a bad idea, that I suggest we, the Internet standards community, do our best to make it not happen.  (I do understand the temptation to think we should make law, but others might disagree :) )   So let's not add any AI features into this standard.

-brewster kahle
Founder, Digital Librarian
Internet Archive