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

RSS Rate limits #4992

Closed
xtrime-ru opened this issue Jan 19, 2022 · 2 comments
Closed

RSS Rate limits #4992

xtrime-ru opened this issue Jan 19, 2022 · 2 comments
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@xtrime-ru
Copy link

Your use case

What would you like to do?

Need ability to control how many requests your backend sends to different data providers.

Why would you like to do it?

Some sources have rate limits. When multiple users add a lot links from same source your server will stuck in blacklist.

Im owner of Telegram -> RSS bridge https://github.com/xtrime-ru/TelegramRSS. Public url: https://tg.i-c-a.su/. And your server constantly exceeds RPM limits.

telegram-cloud-photo-size-2-5417944563953285282-y

I increased RPM for your server as temporary fix.

How would you like to achieve it?

Add table with source/host -> Max RPS relation. Then control how many requests backend generates to such sources.
Also validation would be fine: disable sources with constant errors. For example, if channel removed.

Have you considered any alternatives?

No response

Additional context

No response

@xtrime-ru xtrime-ru added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Jan 19, 2022
@Half-Shot
Copy link
Member

Thanks for the report. I think I understood your request well enough and have opened an issue to track in matrix-org/go-neb#382

@xtrime-ru
Copy link
Author

I checked new issue - it is exactly what i meant. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements
Projects
None yet
Development

No branches or pull requests

2 participants