-
-
Notifications
You must be signed in to change notification settings - Fork 811
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
Please Make a burst mode optional. #92
Comments
read this https://github.com/aahnik/tgcf/wiki/Flood-wait-errors-and-bans and #90 (comment) let flood wait errors occur. when they occur tgcf waits and then resumes. why create an artificial delay when not required ? you are saying to send every 10 seconds, that will take more time to complete the entire thing. i am not interested in going that way. when the rate limit is reached, then wait, and then continue. that's the philosophy of tgcf |
Thank you. You are right. |
I want to comment on this issue. I think a big concern that is on everyone’s mind is that TG will consider the number of messages forwarded as spam and start banning accounts. So without triggering the flood warning the risk will disappear. I agree that the script must be fast. But maybe applying some limits will make it even faster. I know is a bit counterintuitive but hear me out. Currently, the script takes about 10 minutes to forward ~2000 messages and then stops and waits approx. 50 minutes (limit imposed by TG). So in 1 hour can forward 2000 messages. In a day the script can forward ~2000x24=~48.000 messages. For that, it works 10 minutes every hour so in 24 hours works 240 minutes ~4 hours. So the vast majority of time is spent waiting. According to this source TG allows 1 message per second. Currently, the script's speed is ~3.3 messages per second. If the rate is lowered to 1msg/s it will forward 3600 msg/s and ~86.000 msg/day, more than currently does, because even if will forwarding slower it will not waits. Maybe give it a try, make a test build so we can play with it and see the results. |
Oh, I used Google Translate and it was written in Korean by mistake. Ok, I will use English! |
hi @tissole , thank you for your ideas. I will definitely think about this. |
I agree with your opinion. (when they occur tgcf waits and then resumes) I forwarded over 20000 messages with tgcf today, and it was okay! Also, I created a bot, and then tested bulk message forwarding with bot account. I thought bot login is a good alternative, By the way, there were some problems. I discovered this a while ago. After testing several times under controlled conditions, I will post again about this. |
hi @comienzo2093, the rate limit of bot is lower.
so I don't think this can be solved. |
Yes, thank you for your answer. I understood your answer. And I am testing tgcf with 5 accounts, only 1 account is blocked. This was my mistake. I should be careful when chatting while using tgcf. |
@comienzo2093, hmm interesting! Could you give more detail about the account blocked? Was it a new account or an old one? Did you use a normal SIM number phone or virtual number? If it possible can you say from what country? How many messages did you forward before it was blocked? It is a temporary ban or the account is gone forever? Did you talk with Telegram support? @aahnik |
Was it a new account or an old one?
Did you use a normal SIM number phone or virtual number?
If it possible can you say from what country?
How many messages did you forward before it was blocked?
It is a temporary ban or the account is gone forever?
Did you talk with Telegram support?
|
Thank you for the detailed answer. It is very helpful to know what triggers these bans. Another user account was banned in the same conditions: new account and a big number of forwards in a short time. Another element that seems to trigger the bans is the type of phone number. From Telegram: Till now, 3 factors seem to play a role in the bans:
So a prudent approach is to use an old account, a SIM number, and to progressively increase the number of forwards over time. The definitive solution is to prevent altogether these flood messages to occur because these trigger the automation system put in place by TG. Now the limit seems to be 2000 msg/hour, so obeying this limit probably will secure the account in the future. I want to ask you one more thing. Please write to TG @SpamBot and be honest, tell them that you use a script to forward some messages to your channel. At least we will know the TG policy about these scripts and if they lift the ban (I heard that the ban is temporary 24-72 hours). Probably the TG systems confuse the big number of flood msg from an account with a spamming activity. |
hi @tissole this #92 (comment) logic is not correct. if i get time, I will explain in detail later. and stop worrying about rate limits. all apis impose rate limit. that is enforced from the backend server. all these workarounds are useless. |
Is your feature request related to a problem? Please describe.
Sometimes Telegram Account Limited Error occurs. As you know, telegram Account Limited Error is an error which happens when an account sends many messages at once. This does not cause any permanent issues with the account. But When this error happens tgcf will not send any more messages via the account. (Temporary wait limit)
Describe the solution you'd like
It would be very helpful if you provided message rate options.
example : [burst mode - High or Low]
It will be able to reduce the frequency of occurrence of the telegram Account Limited Error.
Describe alternatives you've considered
Alternatively, it would be fine to be able to set the interval between sending messages in seconds.
example: sent every [10] seconds
Thank you! This project is evolving every day.
The text was updated successfully, but these errors were encountered: