Kotlin Telegram Bot API Library (tgbotapi)
160 subscribers
17 photos
1 video
1 file
276 links
https://github.com/InsanusMokrassar/ktgbotapi

Channel with updates from Kotlin Multiplatform TelegramBotAPI library

DM: @InsanusMokrassar
Forum: @ktgbotapi_forum
Projects Releases: @inmodev
Support me: https://t.me/inmodev/431
Download Telegram
Hello everybody :) You may find all the versions of my libraries (including tgbotapi) on my github page. I hope this will be useful for those who is using more than one :)
🤩4
Version 3.2.3 is available. Short highlight about changes since 3.2.0:

• Dependencies updates
• Fixes in DeleteMyCommands
• New reply extensions with chatId and messageId
👍4
I have faced with the new mechanism of stacktrace recovery in coroutines. As I understand, one of the part of this recovery process is to copy old exception into the same new one with the old passing as cause of new.

In two words, we have started to get CommonBotException in CommonBotExceptions 😐

I have fixed this problem in the 3.2.5 and currently preparing 3.2.6 with fix of ChatMember serialization and plan to add requests builders DSL as shown in #657 issue. You are welcome with any suggestions in comments or in my DM about some features/fixes/improvements for lib :)
Hello everybody :) I have started to collect all common plugins for plagubot in one place. So, you are welcome to suggest your plugins for including into the first (0.4.0 😁) version of library
Several small news:

• tgbotapi 3.2.6, 3.2.7: fixes and improvements in buildEntities and keyboard builders
• New Plugins project for PlaguBot with plugins. Currently, some plugins have no readme, but I will fix it soon (I hope)
• PlaguBot 2.3.4 (dependencies update)
Are you ready to kotlin 1.7.20? :)
Anonymous Poll
65%
Yes
4%
No
31%
Wa? What kotlin?
Some time ago Telegram have published their introducing tutorial based on Java, Maven and rubenlagus/TelegramBots. One of our community members have prepared an analogue with our stack: Kotlin, Gradle and InsanusMokrassar/TelegramBotAPI:

https://madhead.me/posts/from-botfather-to-hello-world
5
In new version (3.3.1) will be added new extension "hasNoCommands". Should we use it by default in on content triggers (like onContentMessage)?
Anonymous Poll
57%
Yes
7%
No
36%
Whareve
3.3.1 released 🎉 In two words:

• Dependencies update
• Fixes in multipart requests (thanks to @ithersta report)
• New extensions CommonMessage#hasCommands/CommonMessage#hasNoCommands (thanks to @m_a_d_h_e_a_d contribution)
🎉5
In the Bot API 6.3 new term "forum" has been introduced. Forum is the group chat (supergroup chats, I suppose) with the topics enabled. Currently I am thinking about how to implement it and there are two ways:

• Add new type of chats extending Group/Supergroup
• Add the flag in Group/Supergroup as a sign of forum chat
I plan to rework media groups as content of common messages instead of different types of messages. It is very complex change in API and brings a lot of breaking changes. What would be better in your opinion?
Final Results
53%
Rework everything with Bot API 6.3 - there will be breaking changes anyway
33%
Rework everything in the next major release (maybe right after this release)
13%
Don't touch holy media groups!
Small update :)
🔥2🤯2
So, 4.0.0 has been released 🎉:

• Bot API 6.3 🎉
◦ Forums/topics support
◦ Multiple usernames support
◦ Emojies in chats support
Full rework of media groups
• Dependencies updates

Additionally, I have added new tutorial for work with new media groups to help you adapt your bots with that release 😊
🎉8🔥2👍1
Gladly wish to notify, that since today you may ask your questions and talk about library and related things in special forum on @kotlin_lang