From e5a699161292c4adeaf750130f93b9cd99c3eb99 Mon Sep 17 00:00:00 2001 From: "Andres G. Aragoneses" Date: Sun, 12 Apr 2020 01:57:27 +0800 Subject: [PATCH] README.md: expand on FLOOD_WAIT error Thanks to some inspiration by this comment: https://github.com/sochix/TLSharp/issues/474#issuecomment-611422648 --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0e06b90..5126cbb 100644 --- a/README.md +++ b/README.md @@ -211,7 +211,11 @@ You should create a Telegram session. See [configuration guide](#sending-message #### 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 TgSharp (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 TgSharp to manage more than one telegram account from the same host? If yes, it's likely that you're hitting [Telegram restrictions](https://core.telegram.org/api/errors#420-flood). We recommend that you use TgSharp 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 TgSharp about this, please open a Github issue. #### Why does TgSharp lacks feature XXXX?