Aleksey Usatov
Aleksey Usatov
In all current implementations if errors are caught during polling process (e.g. from my experience `502` is received quite often) all pollers will bombard Telegram servers indefinitely. Something is needed...
Examples of such links in the tdlib: https://github.com/tdlib/td/blob/da4282a6d94c107b3240425b4c72c877eab89b71/td/telegram/LinkManager.cpp#L922-L924
If you've recently started getting an exception with the following message `The request was canceled: A secure channel for SSL / TLS could not be created` it is due to...
Scoped lifetime of `IUpdateManager` and polling functionality built in it don't play well together. An entity that performs polling should be a singleton. `IUpdateManager` functionality should be split to two...
There is a problem with `IBotManager` instances lifetime in webhook mode. Each middleware in ASP.NET Core is instantiated once and is kept in memory as a part of middleware pipeline....
In your current implementation all update handlers share a scope because `getUpdates` can return more than one update at a time. I think it would be better if every individual...
When used with ASP.NET Core 2.0 and `ASPNETCORE_ENVIRONMENT` is set to `Development` and long polling mode is used `UseTelegramBotLongPolling ` throws [this](https://github.com/pouladpld/Telegram.Bot.Framework/blob/master/src/Telegram.Bot.Framework/Extensions/TelegramBotMiddlewareExtensions.cs#L84) exception. Creating explicit scope inside extension methods (`UseTelegramBotWebhook`,...
What do you think of the idea making update handlers more like middlewares is ASP.NET Core which share mutable context instance? That way there could be a common session middleware...
Default timeout in [`GetUpdateAsync`](https://github.com/TelegramBots/telegram.bot/blob/develop/src/Telegram.Bot/TelegramBotClient.cs#L409) method is set to 0. `BotManager` should take timeout from `ITelegramBotClient` and pass it to `GetUpdatesAsync` method. I think there also should be a config for...