IETF Logo Mail Archive

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

Dan Wing <danwing@gmail.com> Mon, 16 December 2024 15:49 UTC

Return-Path: <danwing@gmail.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 93A01C14F6FA for <feeds@ietfa.amsl.com>; Mon, 16 Dec 2024 07:49:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 mhnanb7Bhidr for <feeds@ietfa.amsl.com>; Mon, 16 Dec 2024 07:49:52 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C948C14F60A for <feeds@ietf.org>; Mon, 16 Dec 2024 07:49:52 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id d2e1a72fcca58-725f4025e25so3547026b3a.1 for <feeds@ietf.org>; Mon, 16 Dec 2024 07:49:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734364191; x=1734968991; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=OlRGDqUAah4mnFhigJO6Dfrckf4xekfx2lPizNbu3hk=; b=lKucch4c+8zt1o3YCXd1EG0HdFH+bRxZVRqdE9KsNLNJ4iRVEOQ6Ybs6TkZbKQRO4z Pf+C7H0ZDrl0FTN2GR7PqWVNvAa80a+ESqHkU7OZzA31bRm6e/lRb1SMfxjECawEhce+ 7m20DhOUOSNY6EiomcspLOWYkrjn7wcXucpXx6CwHlAFE8hatD3TOn8AIOu6JbnbClWe fOcwFm5hnYBqscekEiVcWQIC4VDUeACVGKEWYlzQx8P84gMpZF5mRxF5HMregPRFnQNV Y8gv7kAEYzrnrf7F+ELzXCd87+I9o1JByKtEW8Fu7ONtqllMfavviEgrxqLeB8vn6GiZ V2Kw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734364192; x=1734968992; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=OlRGDqUAah4mnFhigJO6Dfrckf4xekfx2lPizNbu3hk=; b=uLGD68SI3jwS2O9OqWRqkCyRpPN02TPcbAoC2gmjkSTJ6FxxX9nubUFs/KZjPXFRen s920BIML+u81Z0GdmJzjhsWhajlc2jPiU7A1rMLzakRGkUevn55i+uWChX+cwvAMDUC3 Q4IptKykLuSyvb1M1XK6bDhvypBpo0pWFR897Bkq4pmYm/7a74cEKMWU3nFbAY1cBd/z 2eghC0Qm6JChY3G3aPOCJl8FMZW+gTOreBQG8ZyxMImbWgSNrEkFdZ4zPGBEIfAk+9ub YqiSArlrpuYEnGlBPNBBwpHp3vLQVWaZnGtMdtbTrAz6sg6Ngv2NuIBxEYqtthe52FBR EfWQ==
X-Gm-Message-State: AOJu0Yxg7XWbueS+PbNvKMc2q6JKrlFguJs09JFnntf+YVUyxqX17uGE UxDL/3sFzsds7j2IH8In1qKhLbByUjAP8rRp9Q1a9zgPBL/W1O4TOhGqRA==
X-Gm-Gg: ASbGncubAPg4npDfxOrAjmfZoNq2LUD3nq+VB7btjDNBSZYwi298WnjBTAIwN1aNGkZ SMOmRIBvZVhy4QdzlkS7t2/K/v4ALFNPWPnvmyK/SfJwiHp+CN8HbUxMAPijO0h4Fdc3rUHMKlY egES2uGmDP/FpaASBzkcYrCte4vVf3cwcLL1cPcA8UqNL41dIVqPh4rttbzsPLj+39iTGbvFun6 +BMPTzwnNgRVdnYYLMaRvBHC7rLtDkrS3B356VSAQ29SJ836yrz0QzSXtSK1MmgMOequzM=
X-Google-Smtp-Source: AGHT+IFDzvmu4Oq+v4hyBeunFBv3OAjjvrqgso1IHDx+3dbguiZkJg1T9xWgrF8V2vNjf/EFpyEbXg==
X-Received: by 2002:a05:6a00:4645:b0:728:e52b:1cc9 with SMTP id d2e1a72fcca58-7290c24d19bmr18923264b3a.18.1734364191441; Mon, 16 Dec 2024 07:49:51 -0800 (PST)
Received: from smtpclient.apple ([47.208.124.206]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-801d5ace24esm4288287a12.39.2024.12.16.07.49.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Dec 2024 07:49:50 -0800 (PST)
From: Dan Wing <danwing@gmail.com>
Message-Id: <D5487AEE-494F-4C3D-AE8D-FBBC8CCBCF44@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BD578CBF-F7A3-4966-B9C0-E96CF7D0B5A3"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\))
Date: Mon, 16 Dec 2024 07:49:49 -0800
In-Reply-To: <tO7MAPewNvEkMpVHZGnnnZiZEBQBv8c4CEvFeNgQuhHi_yiY-SN3Uqf1rc3UYoBXQRkPUKGmzEkkofh2-SebKTiPiebPkc-Nkelv0YQk3aY=@openrss.org>
To: Mark <mark=40openrss.org@dmarc.ietf.org>
References: <tO7MAPewNvEkMpVHZGnnnZiZEBQBv8c4CEvFeNgQuhHi_yiY-SN3Uqf1rc3UYoBXQRkPUKGmzEkkofh2-SebKTiPiebPkc-Nkelv0YQk3aY=@openrss.org>
X-Mailer: Apple Mail (2.3826.200.121)
Message-ID-Hash: G6RGTJ4VE3LNGUHJPDL6TZQYMHQO5BUZ
X-Message-ID-Hash: G6RGTJ4VE3LNGUHJPDL6TZQYMHQO5BUZ
X-MailFrom: danwing@gmail.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
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/sP27UvCSFpz-kUeeDXv1GQqhwVg>
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>

Seems a nice use for a well_known URI, https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml

-d


> On Dec 16, 2024, at 7:13 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 <https://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