More granular RSS rate limiting #13890

New issue

Open

opened 2026-02-22 00:27:05 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-22 00:27:05 -05:00

Owner

Originally created by @MikrySoft on GitHub (Oct 8, 2022).

Suggestion

I propose introduction of per-domain (or per-folder) rate limits to the RSS updater.
If I have x feeds from the same domain (or placed in the same folder, if it's more convenient to implement), I'd like the ability to configure minimal time between requests made to the feed URLs.
For example, I'd like to configure that no two automatic requests made to certain domain are closer than 5 seconds apart.

Use case

Some trackers impose rate limiting on RSS feeds, so if I have multiple feeds configured (different categories, personal vs public etc.), having them all update at once fails.

Extra info/examples/attachments

No response

Originally created by @MikrySoft on GitHub (Oct 8, 2022). ### Suggestion I propose introduction of per-domain (or per-folder) rate limits to the RSS updater. If I have x feeds from the same domain (or placed in the same folder, if it's more convenient to implement), I'd like the ability to configure minimal time between requests made to the feed URLs. For example, I'd like to configure that no two automatic requests made to certain domain are closer than 5 seconds apart. ### Use case Some trackers impose rate limiting on RSS feeds, so if I have multiple feeds configured (different categories, personal vs public etc.), having them all update at once fails. ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

RSS

labels

2026-02-22 00:27:05 -05:00

deekerman commented

2026-02-22 00:27:15 -05:00

Author

Owner

@luzpaz commented on GitHub (Sep 20, 2023):

Linking to #8350

@luzpaz commented on GitHub (Sep 20, 2023): Linking to #8350

deekerman commented

2026-02-22 00:27:15 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**