Re: New web site

Rich Kulawiec <rsk@gsp.org> Fri, 22 May 2026 11:47 UTC

Return-Path: <rsk@gsp.org>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A2051F329ACA for <ietf@mail2.ietf.org>; Fri, 22 May 2026 04:47:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779450432; bh=Xd4GQTdIUtANw7XXiDSVyIaDHqm6M9cP2FyO7hDWANc=; h=Date:From:To:Subject:References:In-Reply-To; b=NqSJ41oCu72j061ovIxw8tbxecS4BFus6+MlIMIbNAiqXNagbac62dMI10rCr5BDb PvmFIFSxxeJ5MIEL1Hxizo4PLAq3ByWnji6FmP1KpHqqrVRc4r8+Q6mAtAj1QD1Z57 6Jy08pxlyRmAkY3pM9oK6DwsLzEM4lBVr+BlNPoM=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=gsp.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 6yky5KJYRGpS for <ietf@mail2.ietf.org>; Fri, 22 May 2026 04:47:12 -0700 (PDT)
Received: from mesa.firemountain.net (mesa.firemountain.net [166.84.136.76]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6B97EF329A12 for <ietf@ietf.org>; Fri, 22 May 2026 04:46:24 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by mesa.firemountain.net (8.18.2/8.18.2) with SMTP id 64MBkI3B078313 for <ietf@ietf.org>; Fri, 22 May 2026 07:46:18 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gsp.org; s=odk; t=1779450378; bh=V4GRPhM1/7cU6ayyhBtKqH9T8p2U83Lw81hHvgOmqRE=; h=Date:From:To:Subject:References:In-Reply-To; b=SX9iu36UEX+QMe4J20FRDhS/cTO7VrvxbYNz5lP1E1FyMfTpmjaBX6BEug9nr6ZHF 9LfBMMjkHSBnN0OTYFWyyZ4uQUU9oKGcaTRfE3/Nc9OVaBLPEtHGM5eYbVrp/Ntu78 8mU2/LpFDSHy6pvjZl/yBY0NTG8ieQLsKDACUMpU=
Date: Fri, 22 May 2026 07:46:18 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: New web site
Message-ID: <20260522114618.GA25004@gsp.org>
References: <AS8PR07MB714328010987A7DEB2ABA7DDC60E2@AS8PR07MB7143.eurprd07.prod.outlook.com> <CAGgd1Oc71QLm8Yp=4v68hc8X36s=0mXcfBX2RzWP=Ch-c+ssBg@mail.gmail.com> <840d0bb4-8b5e-47f5-adaa-5b812bacab2d@cs.tcd.ie> <CAL_px1N-jxPhCHnu50S8fzAsvO2SOeJaFTh=oQoueOtYdtnXvw@mail.gmail.com> <a61bcd14-b17e-4ec6-b5c2-31a8d7c65e31@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <a61bcd14-b17e-4ec6-b5c2-31a8d7c65e31@cs.tcd.ie>
User-Agent: Mutt/1.5.23 (2014-03-12)
Message-ID-Hash: PZJGINXXOHK3QJZJZ44HYCSASNRLANJ2
X-Message-ID-Hash: PZJGINXXOHK3QJZJZ44HYCSASNRLANJ2
X-MailFrom: rsk@gsp.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ecZWQ8F4ZzMoOxTFm1bxkwCiAYg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

On Fri, May 22, 2026 at 12:18:47PM +0100, Stephen Farrell wrote:
> As a heads-up, I'll then complain, also over time:-) I don't think I'm
> entirely alone in preferring a smaller attack surface so it'd be nice if
> the tools team took that into account, as they used to.

You're not alone.  Javascript should be a last resort and should only
be deployed sparingly if no other alternative can be found.  In addition
to increasing the attack surface dramatically, mandating use of Javascript
is hostile to browsers (e.g. text-only browsers) that don't support it,
and thus hostile to the people who use those browsers either by
choice or by necessity.

I would much rather have a non-Javascript site than one with worthless
misfeatures such as "as-you-type search" (mentioned upthread).

---rsk