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
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
• 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)GitHub
Release 3.3.1 · InsanusMokrassar/TelegramBotAPI
Versions:
Ktor: 2.1.2 -> 2.1.3
Klock: 3.2.0 -> 3.3.1
MicroUtils: 0.13.1 -> 0.13.2
Utils:
New extensions on CommonMessage: hasCommands and hasNoCommands. Useful for the initialFilter pa...
Ktor: 2.1.2 -> 2.1.3
Klock: 3.2.0 -> 3.3.1
MicroUtils: 0.13.1 -> 0.13.2
Utils:
New extensions on CommonMessage: hasCommands and hasNoCommands. Useful for the initialFilter pa...
🎉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
• 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!
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 😊
• 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 😊
GitHub
Release 4.0.0 · InsanusMokrassar/ktgbotapi
!!! THIS UPDATE CONTAINS FULL REWORK OF MEDIA GROUPS FUNCTIONALITY !!!
THIS UPDATE CONTAINS BREAKING CHANGES
Common:
All the media groups have been rewritten. Since this update, there are no sepa...
THIS UPDATE CONTAINS BREAKING CHANGES
Common:
All the media groups have been rewritten. Since this update, there are no sepa...
🎉8🔥2👍1
Kotlin Telegram Bot API Library (tgbotapi)
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…
I wished to say additional thanks to @android_broadcast_talks - their admins gave me opportunity to test new topics functionality including topics management and messaging in the threads :)
🔥5
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
Due to the fact of tons changes in the last update, I would be glad to get know about your experience with new media groups and other new/changed API😊
New update 4.1.0 has been released. There is an probability that this version will break some of your code due to the fact that this version brings new types of chats ids:
• IdChatIdentifier - common replacement of old
• ChatIdWithThreadId - additional type of identifier that contains
I hope that this update will not break a lot of your code 😊
• IdChatIdentifier - common replacement of old
ChatId in most cases of chats (ChatId is still presented in library and actual)• ChatIdWithThreadId - additional type of identifier that contains
ThreadIdI hope that this update will not break a lot of your code 😊
GitHub
Release 4.1.0 · InsanusMokrassar/TelegramBotAPI
Versions:
Kotlin: 1.7.20 -> 1.7.21
MicroUtils: 0.14.0 -> 0.14.1
Korlibs: 3.3.1 -> 3.4.0
UUID: 0.5.0 -> 0.6.0
Core:
All the chats identifiers has been rewritten as value classes
New ...
Kotlin: 1.7.20 -> 1.7.21
MicroUtils: 0.14.0 -> 0.14.1
Korlibs: 3.3.1 -> 3.4.0
UUID: 0.5.0 -> 0.6.0
Core:
All the chats identifiers has been rewritten as value classes
New ...
❤1👍1
Latest version is 4.1.2 and here changes since 4.1.0:
• Fixes in
•
• Fixes in
CallbackQuery•
IdChatIdentifier improvements: opportunity to create it with (or without) threadId and FullChatIdentifierSerializer to be able to serialize/deserialize IdChatIdentifier including ChatIdWithThreadIdGitHub
Release 4.1.2 · InsanusMokrassar/ktgbotapi
Versions:
MicroUtils: 0.14.1 -> 0.14.2
BehaviourBuilder:
Fixes in CallbackQuery waiters
MicroUtils: 0.14.1 -> 0.14.2
BehaviourBuilder:
Fixes in CallbackQuery waiters
👏1
Forwarded from inmo.dev
Hello everybody :) I have enabled packages on my gitea instance and started to publish maven packages of most projects there. To include my repo with groovy gradle, add next repository into your
In most of my projects repos sections looks like in the next snippet:
In case you will miss some packages of projects in my repo - you may write in my PM or in comments about that
repositories section:kotlin
maven { url "https://git.inmo.dev/api/packages/InsanusMokrassar/maven" }
In most of my projects repos sections looks like in the next snippet:
kotlin
repositories {
mavenLocal()
mavenCentral()
google()
maven { url "https://git.inmo.dev/api/packages/InsanusMokrassar/maven" }
}
In case you will miss some packages of projects in my repo - you may write in my PM or in comments about that