Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backend: Ability to set feed fetch frequency #1896

Open
Kugelblitz360 opened this issue Oct 4, 2024 · 1 comment
Open

Backend: Ability to set feed fetch frequency #1896

Kugelblitz360 opened this issue Oct 4, 2024 · 1 comment

Comments

@Kugelblitz360
Copy link

I would love to use Newsblur to read some X/Twitter feeds like in the past. There are still Nitter instances around that would work, but if I use their RSS feeds, Newsblur gets shut out frequently because it hits their rate limits.

One thing I can not setup currently in Newsblur is the frequency of requests to the feeds. Ideally I could set up a SCHEDULE for a site, that says "pull every two hours at minute 17". Reason: If I want to see eight twitter feeds in short succession, I again hit a rate limit, but if I have specific minutes for pulls, I can schedule around.

By just having a mechanism where I could setup schedules for specific personal feeds, this would not be a specific "Twitter"/"Nitter" solution but might also come in handy for other services.

Thank you for your consideration,

Boris (docbobo, longtime premium customer)

@samuelclay
Copy link
Owner

That's a great idea. I'd implement this if I had unlimited time, but for now it'll get prioritized on the list. If anybody else has this request, please chime in. And feel free to post this on forum.newsblur.com as an idea, I'd like to see this upvoted!

@samuelclay samuelclay changed the title Suggestion: schedule rate limited RSS feeds (i.e. Nitter) Backend: Ability to set feed fetch frequency Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants