IETF Logo Mail Archive

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

Mark <mark@openrss.org> Mon, 16 December 2024 15:52 UTC

Return-Path: <mark@openrss.org>
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 92731C14F704 for <feeds@ietfa.amsl.com>; Mon, 16 Dec 2024 07:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=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=openrss.org
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 YLH3fE-7CvMK for <feeds@ietfa.amsl.com>; Mon, 16 Dec 2024 07:52:33 -0800 (PST)
Received: from mail-4022.proton.ch (mail-4022.proton.ch [185.70.40.22]) (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 A5A9DC14F60A for <feeds@ietf.org>; Mon, 16 Dec 2024 07:52:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=openrss.org; s=protonmail2; t=1734364351; x=1734623551; bh=DDW2H4bswzZ8JHjt6z/8sRBLTrkMRBDix0PeUKr3NCw=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=DQ/9JtDk9TYgt6SEJW/+DgcSOuuJfrMfaZid3v6XvHuh/HJOIz/ivmLOmGBhz2Kiq p+nB4Ho1Ppv6zKuDTKQaTG4gRWkiV/pRvLDtOEpaXgMdZ+e6YdJl7kHIv8J0V22s/O f5RnOdtt+TBgvRyyJ6XPA6rrS+HaJH9UQ8xNtz854JA2XG5E3pPdbyH/VuxKXBNW9q WOUuNTrZWf0+7BHZIPinAjBBk9ecfVailUNU0NGkof2MXlYn04+qXT1G78VSEN3WAQ M8xKyVXnDLc0ooLDSIQV+V1hn8PZQJb6tVHYqHhZUf0lGqzgpSoVvaYcFwRYvhRMeq HOXCmrb9+UhVg==
Date: Mon, 16 Dec 2024 15:52:25 +0000
To: tim rice <whoneedsgravity@gmail.com>
From: Mark <mark@openrss.org>
Message-ID: <k95ohlMWo-dIuRvCVX0Je6EuOd6XhLKktaI33GYzFQb5iGgq7iMPAMMRX0o65QJOE8sEkCtwyfPUUoXu6bNYvaGN59rNjFrqyFYtaWYr8Jo=@openrss.org>
In-Reply-To: <CABJ24q1Svdg3E8tw4UTxsOhaTntdGsjSQfMOiT4z9ecmxw=t=g@mail.gmail.com>
References: <tO7MAPewNvEkMpVHZGnnnZiZEBQBv8c4CEvFeNgQuhHi_yiY-SN3Uqf1rc3UYoBXQRkPUKGmzEkkofh2-SebKTiPiebPkc-Nkelv0YQk3aY=@openrss.org> <CABJ24q1Svdg3E8tw4UTxsOhaTntdGsjSQfMOiT4z9ecmxw=t=g@mail.gmail.com>
Feedback-ID: 62933185:user:proton
X-Pm-Message-ID: 91919e73a4e00c48849ab88554caa8d2108f629d
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1=_Uk58mMxwIXxtbD3Rrb9AmHxnHsSNWrSwY6f2EQO0hM"
Message-ID-Hash: ZN77CW2YFLMSXPCFB4QXBQRQL2S5CK4M
X-Message-ID-Hash: ZN77CW2YFLMSXPCFB4QXBQRQL2S5CK4M
X-MailFrom: mark@openrss.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
CC: "feeds@ietf.org" <feeds@ietf.org>
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/bfwN6OjlVWW_EgYlgyVkPb2wNBg>
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>

Hey Tim,

Oh I'm not a part of the working group.
Your question is precisely why I'm inquiring about it. I'd love to know what the recipients of this mailing list think about it, whether or not standardizing on a RSS feed path makes sense discussing in this group, or if the idea even makes sense at all. :)

Mark Kennedy
Engineer
openrss.org

On Monday, December 16th, 2024 at 10:22 AM, tim rice <whoneedsgravity@gmail.com> wrote:

> Morning Mark,
>
> Is this within the purview of the IETF, and does a similar standard for the other examples that you mentioned exist already?
>
> Thank you,
>
> -Tim
>
> On Mon, Dec 16, 2024 at 7:15 AM Mark <mark=40openrss.org@dmarc.ietf.org> wrote:
>
>> Hey,
>>
>> My org works on providing RSS feeds for websites that don't have them. And we're seeing a lot of feed readers adopting the unfortunate practice of probing multiple paths to a website just to try to find if there's an RSS feed available (e.g. /rss, /.xm, /feed, etc). It hogs up quite a bit of unnecessary resources. It becomes an even harder hit for servers when all the requests happen at the exact same millisecond. :(
>>
>> We could benefit from standardizing on a single path so that feed readers can easily find a site's RSS feed. Kind of like the robots.txt file or the favicon.ico file. Everyone knows where they are.
>>
>> Has the working group ever discussed something like this? I'm curious of your thoughts.
>> Thanks and hope your week is off to a great start!
>>
>> Mark Kennedy
>> Engineer
>> openrss.org
>>
>> --
>> Feeds mailing list -- feeds@ietf.org
>> To unsubscribe send an email to feeds-leave@ietf.org

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