Ruben Bermudez

@Chase22 Happy to redesign part of those core componenes, as long as we keep the functionality of them: - Only one consumer thread from Telegram server - No breaking changes...

@Chase22 Probably we can take this chance to remove the HttpClient from Oracle and move into the standard one from Java 11

@Chase22 Was thinking about this redisign and I'd be up to split the library in 4 base modules/jars: - telegrambots-meta: as it is now (probably some things being removed) -...

My idea is that users can choose to implement their own versions of the longpolling/webhook if they want while getting most of the logic to send messages out of the...

Agree, it can be named something like telegrambots-base or similar. I'll try to create a branch with the initial idea (naming can be decided later)

Methods are just a representation of the different API methods: https://core.telegram.org/bots/api#promotechatmember You just need to set the needed fields and then execute the methods

@shalupov Have you seen any case when throwing a `Error` inheritor makes sense to keep running the process? They usually imply bigger problems that the applications won't easily be able...

@NiceCraftz Solved? Good to close?

@stefan-kolb It was added to the [How-To-Update](https://github.com/rubenlagus/TelegramBots/wiki/How-To-Update#to-version-32) guide.

Just to simplify the API since internally they were already callling same code. Now all those request can be done calling `execute` or `executeAsync`