Kotlin Telegram Bot API Library (tgbotapi)
159 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
Version 0.37.3 (0.37.2 was published with one critical issue, so, I published quick fix 0.37.3) is available in maven central. In two words:

• Update up to Telegram Bot API 5.5
• Fix of EntitiesBuilder#linkln
• Dependencies updates

Report on some issues or suggestions in comments or just in discussion group :) currently next update is planned for #511 Issue (about extension to make this library looks like common Telegram Bot API)
Forwarded from Telegram Info (Полян)
Bot API был обновлён до версии 5.6

Что нового:
Улучшена поддержка функций защищенного содержимого.
— В методы добавлен параметр protect_content: sendMessage, sendPhoto, sendVideo, sendAnimation, sendAudio, sendDocument, sendSticker, sendVideoNote, sendVoice, sendLocation, sendVenue, sendContact, sendPoll, sendDice, sendInvoice, sendGame, sendMediaGroup, copyMessage, forwardMessage.
— Добавлена поддержка «спойлеров», которые будут работать в версиях Telegram, выпущенных после 30 декабря 2021 года. Более старые клиенты будут отображать неподдерживаемое сообщение.
— Добавлен новый тип MessageEntity "spoiler".
— Добавлена возможность указывать объекты спойлера, используя параметры форматирования HTML и MarkdownV2.

Полный список изменений на официальном сайте.

#обновление #BotAPI
So, there are several news:

• Version 0.37.4 of tgbotapi has been released. It contains mostly improvements from this PR (thanks to madhead)
• New Telegram Bot API version 5.6 has been released too. In that release there are several protecting content improvements and opportunity to add and use spoilers
• That has happend - all necessary dependencies were updated up to Kotlin 1.6 and I've started 0.38.0 version. I plan to add there support for Telegram Bot API 5.6 and solve at least some parts of #511 issue
Besides, I wish you happy holidays, happy new year and bots without bugs 🎉
2🎉2
In case this library will be updated up to kotlin 1.6, will you be ready to migrate too?
Anonymous Poll
100%
Yes
0%
No
👍3
🔥4
Kotlin Telegram Bot API Library (tgbotapi) via @TGStat_Bot
Photo
Our humble statistic 😊 Thank you for your critics, support and help :)
0.38.0 version of update has been released :) here mainly update up to Kotlin 1.6, update up to Telegram Bot API 5.6 and several fixes
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.0

This update contains Telegram Bot API 5.6 implementation

This update contains migration onto Kotlin 1.6

This update has changed constructors of all CommonMessage implementations


Common:
Version:
Kotlin: 1.5.31 -> 1.6.10
Coroutines: 1.5.2 -> 1.6.0
Serialization: 1.3.1 -> 1.3.2
Klock: 2.4.8 -> 2.4.10
Ktor: 1.6.5 -> 1.6.7
MicroUtils: 0.8.7 -> 0.9.0
Core:
• Add SpoilerTextSource (as part of Telegram Bot API 5.6 update)
• Add support of protect_content as a field protectContent in all send message requests and parameter in all functions related to that requests (as part of Telegram Bot API 5.6 update)
ALL IMPLEMENTERS OF CommonMessage HAS CHANGED THEIR CONSTRUCTOR: NOW THEY GET hasProtectedContent instead of forwardable (inversed) field
ChannelContentMessageImpl
ChannelMediaGroupMessage
CommonMediaGroupMessage
GroupContentMessage implementers
ConnectedFromChannelGroupContentMessageImpl
UnconnectedFromChannelGroupContentMessageImpl
AnonymousGroupContentMessageImpl
CommonGroupContentMessageImpl
PrivateContentMessageImpl
👍2
0.38.1 PR is in work and I hope today I will release this version. Currently it is still in progress and you may offer some features to include in this update ☺️
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.2

Common:
Version:
MicroUtils: 0.9.0 -> 0.9.1
API
• New extensions TelegramBot#copyMessages for media groups
1
Hello :) in 0.38.2 I wished to add media groups sending methods with content lists, but due to the signature clash I can't add methods with names like sendMediaGroup due to their existance with input media lists.

How do you think, which names in that case would be better to choose for media groups sending by content? Add prefix or postfix like sendContentMediaGroup? Or something else? I would be glad to see your opinion :)
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.3

Common:
Version:
MicroUtils: 0.9.1 -> 0.9.2
Klock: 2.4.10 -> 2.4.12
UUID: 0.3.1 -> 0.4.0
API
• New extensions TelegramBot#send• for media groups with contents
Release 0.38.4 is available in maven central. Here:

• Fix of #529
• Realization of Telegram Bot API 5.7, including:
• Separation of Sticker to SimpleSticer, AnimatedSticker and VideoSticker
2🔥1