Skip to content
This repository has been archived by the owner on Apr 27, 2020. It is now read-only.

Work around message flood limit #121

Open
SebiderSushi opened this issue Jul 30, 2018 · 1 comment
Open

Work around message flood limit #121

SebiderSushi opened this issue Jul 30, 2018 · 1 comment

Comments

@SebiderSushi
Copy link

SebiderSushi commented Jul 30, 2018

Since the 400 messages per 30 seconds flood limit doesn't seem to apply to the new official data export tool in Telegram Desktop 1.3.8+, could there be any way to achieve the same thing for telegram_backup?
It's probably too complicated or even impossible since being able to use their method from Telegram Desktop for arbitrary requests would disable Telegrams flood protection which obviously isn't desired to be easy but there's always hope i guess.

Also for people who want to create a backup of a huge account using telegram_backup a feature to import a .json File of all messages created by the Telegram Desktop data export tool would already be super helpful.

@SebiderSushi SebiderSushi changed the title Workaround message flood limit Work around message flood limit Jul 30, 2018
@SebiderSushi
Copy link
Author

I once did some tests fiddling with the telegram API. Back then i came to the conclusion that the flood limit is as low as 400 messages per 30 seconds only while getting the messages by their consecutive IDs. Telegram Desktop is fetching messages per chat/channel/group and uses the appropriate API for that, which isn't rate limited (that strictly) and also doesn't return empty (deleted) messages.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant