Open spotlightishere opened 5 years ago
Can you please write down the steps to reproduce this issue?
I no longer have the exact code, but it recursed throughout history and forwarded messages to a channel. I ran the thing multiple times over in say an hour, assuming that perhaps it was too much for its mutex to handle.
For the second, that snippet is all I kept as an example, unfortunately.
I ran code with the assumption
err
would return upon any limiting. After messages failed to send, I turned the TDLib logging level to find Telegram was repeatedly responding with 429 Too Many Requests and the amount of seconds to wait. My account was banned off Telegram over such. (Since such, it was restored after requesting.)Additionally, the enum/interface/etcetera given from the UpdateNewMessage receiver isn't usable with my knowledge of how it'd work. (Please correct me if I'm not using Go properly.)
is invalid as
MessageSendingState is also the same way.