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

Delay for forwards #99

Closed
raffnix204 opened this issue Feb 26, 2024 · 1 comment
Closed

Delay for forwards #99

raffnix204 opened this issue Feb 26, 2024 · 1 comment

Comments

@raffnix204
Copy link

raffnix204 commented Feb 26, 2024

Hello,
thank you for the tool, it's great and works very well. The only problem I have is that i sometimes have a delay from 10-30 seconds. Sometimes its only 1 second what is fine because for my use case, I need as minimal delay as possible. Are there ways to reduce the delay, could it be due to the code or is it related to the Telegram API or the source channels?
I tried different settings and have a minumum config (only in .env file - i dont use the filter file):
Thats how my .env file looks:
API_ID=123
API_HASH=123
SESSION_STRING=123
USE_MEMORY_DB=true
CHAT_MAPPING=[-10012345678:-10012345678910];
YAML_CONFIG_ENV=\ndisable_edit: true\ndisable_delete: true\nmode: forward\n\n# (Required) Mirror directions\ndirections:\n - from: [-10012345678:]\n to: [-10012345678910]\n\n

The new message in the source channel gets recognized sometimes with a lot of delay, i watched it live now and the tg timestamp of the source channel was: 20:55:13
Then nothing happened a long time and then the messagee showed up in cli:
INFO 2024-02-26 19:56:02,874 [mirroring.py:69]:telemirror: [New message]: https://t.me/c/123254346/25352

And then the message got delivered in my channel with the timestamp 20:56:04.
Do you have any idea to improve that?

Best regards

@raffnix204 raffnix204 changed the title Delay from forwards Delay for forwards Feb 26, 2024
@khoben
Copy link
Owner

khoben commented Feb 27, 2024

It depends on the internal Telegram's sending logic. Try to get a new session, reduce channel subscriptions. Also try with a different account.

@khoben khoben closed this as completed Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants