sochix/TLSharp
1
0
Fork 0
mirror of https://github.com/sochix/TLSharp.git synced 2025-12-06 08:02:00 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

README.md: expand on FLOOD_WAIT error

Browse source 
Thanks to some inspiration by this comment:
https://github.com/sochix/TLSharp/issues/474#issuecomment-611422648
This commit is contained in:
Andres G. Aragoneses 2020-04-10 15:07:02 +08:00
parent c67801a6c9
commit 7fb4a0f8a7
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -203,7 +203,10 @@ TLSharp library should automatically handle these errors. If you see such errors
You should create a Telegram session. See [configuration guide](#sending-messages-set-up)
#### Why do I get a FloodException/FLOOD_WAIT error?
It's likely [Telegram restrictions](https://core.telegram.org/api/errors#420-flood), or a bug in TLSharp (if you feel it's the latter, please open a Github issue). You can know the time to wait by accessing the FloodException::TimeToWait property.
After you get this, you cannot use Telegram's API for a while. You can know the time to wait by accessing the FloodException::TimeToWait property.
If this happens too often and/or the TimeToWait value is too long, there may be something odd going on. First and foremost, are you using TLSharp to manage more than one telegram account from the same host(server)? If yes, it's likely that you're hitting [Telegram restrictions](https://core.telegram.org/api/errors#420-flood). We recommend that you use TLSharp in a standalone-device app (so that each instance of your program only uses one telegram account), so for example a mobile app, not a web app.
If, on the other hand, you're completely sure that you found a bug in TLSharp about this, please open a Github issue.
#### Why does TLSharp lacks feature XXXX?