Switch account, when flood wait limits one account for a long period of time

See original GitHub issue

Background When using the bot for large amounts of forwarding (thousands of messages and files each day), there is a floodwait enforced from the Telegram API. This floodwait varies and sometimes you can hit a long wait time of hours or a temporary suspension of 24 hours.

Workaround If we have multiple Telegram Accounts, we can setup multiple Apps and API users / Bots. This means we can just delete the .forwardersession file and start again on another account.

Request Enhance the Telegram Chat Forward bot to allow for it to alternate between various Telegram API users and .forwardersession files to avoid this ban.

Sample Viable option: Have multiple api_id and hash stored in the .env file and anytime a floodwait error is over X amount of seconds (300 etc) then switch to the next api_id / hash in the file: api_id_1=302XXX api_hash_1=7exxxxxxx api_id_2=303XXX api_hash_2=7fxxxxxxx

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:7 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
aahnikcommented, Mar 6, 2021

Fantastic idea.

Actually, I am restructuring the code for a lot of reasons.

I will try to implement this feature in the new version. In the new version (upcoming), you can also login using a bot account. (and not your user account)

This is to terminate the risk of your account getting banned.

The bot that will do the forwarding must be in the source as well as destination channel/group. If the source channel is not owned by you, you will not be able to reap the feature.

0reactions
aahnikcommented, May 8, 2021

if you want to use multiple accounts, you need to do that manually. create two different folders. and create different sessions.

automatic client switching in the middle of forwarding will add unnecessary complexity.

after the introduction of custom_delay, you are less likely to face 1 day suspensions.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Telegram API throwing PeerFloodError after sending 50 ...
Telegram API throwing PeerFloodError after sending 50 messages at a sleep time of 120 seconds · Your account will receive a peer flood...
Read more >
V. Lending - Flood Insurance Questions & Answers - FDIC
There is no waiting period when an additional amount of NFIP insurance is required in connection with the making, increasing, extending or renewing...
Read more >
National Flood Insurance Program April 2021 Flood ... - FEMA
April 1, 2021. Dear National Flood Insurance Program Flood Insurance Manual User: ... Map Revision Exception (1-Day Waiting Period) .
Read more >
Why has Telegram refused to make me log in, telling me, 'too ...
The reason of causing PEER FLOOD error could be your account limitation or the network you are using to connect to Telegram server....
Read more >
Time Limit for Car Insurance Claim Settlement - Progressive
How long does it take to get a settlement check after a car accident? The amount of time it takes to settle an...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found