IETF Logo Mail Archive

[Feeds] Re: Should we standardize on a single URL path to RSS feeds?

John Levine <johnl@taugh.com> Mon, 16 December 2024 18:43 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: feeds@ietfa.amsl.com
Delivered-To: feeds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D063BC1CAE98 for <feeds@ietfa.amsl.com>; Mon, 16 Dec 2024 10:43:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level:
X-Spam-Status: No, score=-1.856 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=iecc.com header.b="Yj0nNORn"; dkim=pass (2048-bit key) header.d=taugh.com header.b="mQ2YR3nx"
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 OEZxAfe0_dYP for <feeds@ietfa.amsl.com>; Mon, 16 Dec 2024 10:43:35 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 ietfa.amsl.com (Postfix) with ESMTPS id C205AC1CAE94 for <feeds@ietf.org>; Mon, 16 Dec 2024 10:43:34 -0800 (PST)
Received: (qmail 98458 invoked from network); 16 Dec 2024 18:43:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=18097676074d4.k2412; t=1734374602; x=1734720202; bh=AtqR7Olp1VulcvJXJ8q6xO0rvzHgXsdJ1XMP/AFYEuE=; b=Yj0nNORn9yJrBhxx8UAi8U4d9fHky54pbSGXLla9ByGO4Fd7BwcJAJW1hjZanOI+vVrXE4ujas97v3n3uikDGxn6CXLQP8MNWFwfMctT/pmwO1azhzw3Pvrp0MRKKDToZxH9ec83x26imrE3oBXPPrGDqe8eY8nkRkgI6er/AR0xEEAZg1/J3ticBysC9y6zAVhDWL9v0uyLhUIL/KYkUab5LUB5ChetsBDN1ox6xFGxWx3T6z0w0Pr0lZLW8HWnYaBLoow5GfTWGM7xg9QyNutEvKrEblog4QOReegTPD/NE73pX4zWeIMzpzdEwJNHLD+rlYZAIoraSxEhkhBJNA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=18097676074d4.k2412; bh=AtqR7Olp1VulcvJXJ8q6xO0rvzHgXsdJ1XMP/AFYEuE=; b=mQ2YR3nxsrQCAyXHz6QCdukCNV89Z/PsU0mcBsEqeDgcVCAHCHGDo3ODNqeKUfRhTgFAz7xLOlX5BdaGne5//LRTIYxo6M7lEOTGX18mnxkK41NOLl0bIGruMK4Q3+nWjvRnMlk5B9V+tgZaWHiNQisug1q81Xk2DXi1GEarlc+UOtDh7O3B7WHV9jO1Wekud9VQXA+XN/MqN07dTGtzfg2Ai/PtvSxkuGKsTaEuF++jS2GOiq1MauvTlEO28/3ZdDFFMqv44N2xngJcR7REA8ZH6MK3mu7Qsk4u7q/8pXLuCZkZusNNw9b2jEI2u565owMdVuHcAAzcwkMFhb/7UQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 16 Dec 2024 18:43:31 -0000
Received: by ary.qy (Postfix, from userid 501) id 67789AE8BF9E; Mon, 16 Dec 2024 13:43:30 -0500 (EST)
Date: Mon, 16 Dec 2024 13:43:30 -0500
Message-Id: <20241216184331.67789AE8BF9E@ary.qy>
From: John Levine <johnl@taugh.com>
To: feeds@ietf.org
In-Reply-To: <2Z5-Z8IoyYo4I6bYSYf0S6rjcBCca1iDrOiLXg_3d_hxpVy6vcdeG7ReReT7c78-fBmuyNdIfP2MccbYzUv1WVJLMsWfozmuXMM7-JDJgsc=@openrss.org>
Organization: Taughannock Networks
References: <AS2P195MB215516B84E13D13DE097C2249E3B2@AS2P195MB2155.EURP195.PROD.OUTLOOK.COM> <2Z5-Z8IoyYo4I6bYSYf0S6rjcBCca1iDrOiLXg_3d_hxpVy6vcdeG7ReReT7c78-fBmuyNdIfP2MccbYzUv1WVJLMsWfozmuXMM7-JDJgsc=@openrss.org>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: ZLWB5R7QG7ABGSB6GGUGJW3LVZEQAJ2P
X-Message-ID-Hash: ZLWB5R7QG7ABGSB6GGUGJW3LVZEQAJ2P
X-MailFrom: johnl@iecc.com
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: [Feeds] Re: Should we standardize on a single URL path to RSS feeds?
List-Id: Web Feeds <feeds.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/feeds/34PV67STkBIpVJn8zf3rl-agUTc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/feeds>
List-Help: <mailto:feeds-request@ietf.org?subject=help>
List-Owner: <mailto:feeds-owner@ietf.org>
List-Post: <mailto:feeds@ietf.org>
List-Subscribe: <mailto:feeds-join@ietf.org>
List-Unsubscribe: <mailto:feeds-leave@ietf.org>

It appears that Mark  <mark@openrss.org> said:
>-=-=-=-=-=-
>That's a great question!
>
>The problem with the link tag autodiscovery approach is that we see many feed publishers will change their RSS feed paths (not provide a redirect) and forget to update the link, making the link tag unreliable. This
>issue wouldn't exist if there's an actual standardized path that we can assume all RSS feeds are located.

I think you're way too optimistic.  If they can't be bothered to put one line of HTML in
the web page, why do you think they'd read a new spec and put the feed in a new place?

While I don't think there's anything wrong with defining a .well-known URL for RSS feeds,
I also think you can't fight stupid so don't get your hopes up.

R's,
John

v2.31.3 | Report a Bug | By Email | System Status