Why i get rpc_error FLOOD_WAIT about tlsharp HOT 23 CLOSED

See this https://core.telegram.org/api/errors#420-flood

from tlsharp.

Ok. I got it. then how many attempts of one method i can invoke?

from tlsharp.

I don't know

суббота, 3 октября 2015 г. пользователь starbug1 написал:

Ok. I got it. then how many attempts of one method i can invoke?

—
Reply to this email directly or view it on GitHub
#12 (comment).

Best regards, Ilya (http://sochix.ru)
С уважением, Илья (http://sochix.ru)

from tlsharp.

Ok. I got it. then how many attempts of one method i can invoke?

Put a delay of 2 seconds between invokes.

from tlsharp.

@delphiassistant : Thanks. i placed delay of 2500 between every method's invoke, but after almost 10 request FLOOD_WAIT error occur and say you should wait for example 270 sec. and because i need to send bulk requests to telegram what i must do to pass this error. Thanks.

from tlsharp.

Yeah and ahhh....
I seen it as well. it's not 10, that delay is per 9 request and is really
frustrating.
This occurs after 9 invokes to send message too.
در تاریخ ۴ اکتبر ۲۰۱۵ ۱۹:۳۰، "starbug1" [email protected] نوشت:

@delphiassistant https://github.com/delphiassistant : Thanks. i placed
delay of 2500 between every method's invoke, but after almost 10 request
FLOOD_WAIT error occur and say you should wait for example 270 sec. and
because i need to send bulk requests to telegram what i must do to pass
this error. Thanks.

—
Reply to this email directly or view it on GitHub
#12 (comment).

from tlsharp.

@delphiassistant: then you say telegram server works with count of requests not with (count/time)? i mean count of requests in time unit is not important?

from tlsharp.

I can't say exectly which parameter is important.
در تاریخ ۴ اکتبر ۲۰۱۵ ۲۱:۵۸، "starbug1" [email protected] نوشت:

@delphiassistant https://github.com/delphiassistant: then you say
telegram server works with count of requests not with (count/time)? i mean
count of requests in time unit is not important?

—
Reply to this email directly or view it on GitHub
#12 (comment).

from tlsharp.

@starbug1,did you find solution for flood_wait?

from tlsharp.

Not yet. It's limit is too dumb. 9 Requests and time is not important.

from tlsharp.

mr keramati,You have worked with telegram API?

from tlsharp.

Sure.

from tlsharp.

@eslamih10: as delphiassistant said there is a maximum number of attempts of one method. but if you can delete your session and recreate it under 200 second(for every usual waits), then you can do what you want.

from tlsharp.

@delphiassistant,Did you use Visual studio 2013 or 2015?

from tlsharp.

@starbug1,Unfortunately,When I delete the session, there is still the problem!

from tlsharp.

you must delete session. and create it again and add the code you get from telegram to it.this process must be done under logic time.

from tlsharp.

as delphiassistant said there is a maximum number of attempts of one method. but if you can delete your session and recreate it under 200 second(for every usual waits), then you can do what you want.

This will be a tedious task since you will need to get another authentication code from telegram and add it into the code.

Did you use Visual studio 2013 or 2015?
VS2015.

Unfortunately,When I delete the session, there is still the problem!
It seems to be based on invoker ip address.

from tlsharp.

@delphiassistant: you can do this programatically. not with your hands. just be a bit creative.

from tlsharp.

You mean by having telegram client app open, and using windows hooks?

from tlsharp.

it means There is Not A Soultion For Preventing This Error?

from tlsharp.

@starbug1 Delete session.dat file? how?

from tlsharp.

I solved this issue. please send your question in my group:
https://t.me/joinchat/HhLHow3Ed97A0gRZo7Ggog

from tlsharp.

@mostafa8026 Foolish!

from tlsharp.