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
KDocs and Bookstack are currently unavailable, but the most part of information is available in the project wiki and source code (of course :) ). I plan to up bookstack and kdocs asap and will notice about it when they will be available again
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.8

Common:
Version:
MicroUtils: 0.9.12 -> 0.9.16
Klock: 2.6.2 -> 2.6.3
Ktor: 1.6.7 -> 1.6.8
BehaviourBuilder:
• Fixes in onMediaGroup and dependent functions
• Add several new extensions for SimpleFilter:
SimpleFilter#listAll
SimpleFilter#listAny
SimpleFilter#listNone
Besides, wished to announce that Bookstack must be available (or must become available in near time)
KDocs is available again :) There is a probability that after 22th of March it become unavailable, but I will try hard to avoid or fix it if that will happen
👍3
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.9

Core:
• New function MessageContent.Companion#serializationModule
• Now it is possible to create TelegramBot (RequestsExecutor) with several bots under the hood and opportunity
for bots requests load balancing or fault-fix via sending of the requests via another bot
API:
• Add replies which will use another message as a source for reply (copyMessage)
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.10

API:
• All with•Action extensions got a contracts which declare that block will be called once
• Add several extensions TelegramBot#sendPhoto with PhotoSize
• Add several extensions TelegramBot#reply with PhotoSize
In the Bookstack tutorials became available simple BehaviourBuilderWithFSM tutorial
Hello everybody :) I am collecting an ideas for the 1.0.0 version and invite you to include your suggestions there. That release will allow breaking changes and you may admit even the things which could lead to some deep rework 😊
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.11

Common:
Version:
MicroUtils: 0.9.16 -> 0.9.17
Klock: 2.6.3 -> 2.7.0
Core:
• Fixes in TextSourcesList creating in from RawMessageEntities
• Old ways to create keyboards (matrix and row) have been deprecated
API:
• Add ability to reply with Poll
• Add ability to reply with any MessageContent
• Add ability to reply with any TelegramMediaFile
Migrate to 1.6.20? I doubt beacause currently there are problems with the other dependencies which do not support 1.6.20 (like jb-compose). If we will upgrade library, it will be possible to make library more strictly in future. What do you think?
Final Results
71%
Yes, lets make step forward :)
29%
No, I want to get updates without problems
I hope, soon it will be implemented in our lib😊
Forwarded from BotNews
Bot API 6.0

• Added support for Web Apps.
KeyboardButton and InlineKeyboardButton can now be used to launch Web Apps.
• Added control over the bot's menu button via setChatMenuButton and getChatMenuButton.
• Added control over the bot's default admin rights via setMyDefaultAdministratorRights and getMyDefaultAdministratorRights.
• Added support for t.me links to add bots as admins.

• And more, see the full changelog for details:

https://core.telegram.org/bots/api-changelog#april-16-2022

Warning: After the next update, login_url will only allow HTTPS links.
Attention: this update DOES NOT CONTAIN update up to Telegram Bot API 6.0
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.13

Core:
• Fixes in mention creation
• Deprecate StorageFileInfo
BehaviourBuilder:
• In the expectations a lot of on•Message extensions have been added (like onContentMessage). These extensions could be useful when with the Content its message info is important
Hello everybody :) With support of Telegram Bot API 6.0 I plan to release version 1.0.0 (PR). Currently there is one difficult choice:

• Potentially make break changes and fix all the things which is possible to fix in that release
• Do not make a lot of break changes, but fix some things

Besides, it looks like this release will not contain update up to kotlin 1.6.20 (😔) due to the fact that currently I can't update MicroUtils because of JetBrains Compose still not support new kotlin