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
Hello everybody :) I am preparing new fix-update, but fix-updates also may contains some features :) so, I would be glad to know about the things you want to see in this library :)
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 4.1.3
GitHub
Release 4.1.3 · InsanusMokrassar/ktgbotapi
Versions:
MicroUtils: 0.14.2 -> 0.14.4
Core:
ContentMessage, CommonMessage, PossiblyMediaGroupMessage and PossiblySentViaBotCommonMessage got out
variance
UserId now is ChatId instead of IdC...
MicroUtils: 0.14.2 -> 0.14.4
Core:
ContentMessage, CommonMessage, PossiblyMediaGroupMessage and PossiblySentViaBotCommonMessage got out
variance
UserId now is ChatId instead of IdC...
👍1
Happy new year! I wish you all in new year to avoid any negative consequences of wrong decisions of the third party, to release your plans and wishes and create the best bots! 🎉
Just in any case: 5.0.0 with Bot API 6.4
Just in any case: 5.0.0 with Bot API 6.4
GitHub
Release 5.0.0 · InsanusMokrassar/TelegramBotAPI
Bot API 6.4 support!
Long-polling improvements
Long-polling improvements
❤4👍2🎉2
Should we migrate onto 1.8? It mostly brings fixes and should not have some breaking changes, but I am not sure
Anonymous Poll
67%
Yes
0%
No
33%
Kotlin 1.2.10 is the best 🌚
Small fixes/version updates release
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 5.0.1
GitHub
Release 5.0.1 · InsanusMokrassar/TelegramBotAPI
Versions:
MicroUtils: 0.16.4 -> 0.16.6
Ktor: 2.2.1 -> 2.2.2
Core:
Fixes in SendMediaGroup request
Fixes in SetChatAdministratorCustomTitle request (thanks to @madhead)
MicroUtils: 0.16.4 -> 0.16.6
Ktor: 2.2.1 -> 2.2.2
Core:
Fixes in SendMediaGroup request
Fixes in SetChatAdministratorCustomTitle request (thanks to @madhead)
🎉3😁1
Today I realised that, maybe, 5.0 version should be the 1.0. It is related to several things:
• More or less stabilized API
• Useful DSLs for different cases such as comfortable logic builders and keyboards DSLs
• All the API covered and most of Telegram API cratches are hidden (e.g. media groups)
• A lot of fixes has been applied
Anyway, thanks to all who has been involved in the development or providing feedback.
And welcome to those who is new in this library :)
• More or less stabilized API
• Useful DSLs for different cases such as comfortable logic builders and keyboards DSLs
• All the API covered and most of Telegram API cratches are hidden (e.g. media groups)
• A lot of fixes has been applied
Anyway, thanks to all who has been involved in the development or providing feedback.
And welcome to those who is new in this library :)
❤5
Hello everybody :) Telegram Bot API 6.5 has been introduced and I plan to cover it in our library in several days.
Anyway, it is expected that today/tomorrow I will release version 5.0.2 and I think it will be the last version on kotlin 1.7 and 5.1.0 with Bot API 6.5 should work on 1.8.10
Anyway, it is expected that today/tomorrow I will release version 5.0.2 and I think it will be the last version on kotlin 1.7 and 5.1.0 with Bot API 6.5 should work on 1.8.10
Cover Bot API 6.5 with kotlin update up to 1.8.10?
Anonymous Poll
65%
Yes, why not
10%
No, it is better to actualize kotlin in new version
25%
GIVE ME BOT API 6.5
Small preview of update 6.5:
+ Buttons for requesting of users and chats, but:
- They are reply buttons and can be sent only in reply keyboard
+ Granular permissions for more accurate settings in chats
- For backward compatibility (as I understand) they have disabled by defailt and currently it is not clear, what will be used as replacement for what. In API there are several notes about it, but they are strange: send polls permission as replacement of send messages in granular mode, for example
UPD: Anyway, tomorrow I plan to test permissions and make some final fixes for this update
+ Buttons for requesting of users and chats, but:
- They are reply buttons and can be sent only in reply keyboard
+ Granular permissions for more accurate settings in chats
- For backward compatibility (as I understand) they have disabled by defailt and currently it is not clear, what will be used as replacement for what. In API there are several notes about it, but they are strange: send polls permission as replacement of send messages in granular mode, for example
UPD: Anyway, tomorrow I plan to test permissions and make some final fixes for this update
core.telegram.org
Bot API changelog
The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram. To learn how to create…
👍2
5.1.0 with support of 6.5 has been released 🎉 I have upgraded examples with two new samples: for new separated rights and for new buttons
GitHub
Release 5.1.0 · InsanusMokrassar/TelegramBotAPI
Bot API 6.5 support
Core:
ChatPermissions now is interface and have two main realizations: ChatPermissions.Granular and
ChatPermissions.Common
RestrictedChatMember now implements ChatPermissions ...
Core:
ChatPermissions now is interface and have two main realizations: ChatPermissions.Granular and
ChatPermissions.Common
RestrictedChatMember now implements ChatPermissions ...
🎉3
5.2.1 has been released. What has happen since 5.1.0:
• Traditional minor dependencies updates
• All
• Sent messages waiters in behaviour builder will not be triggered on edited messages
•
• Traditional minor dependencies updates
• All
CallbackQuery now accepts CommonUser instead of User• Sent messages waiters in behaviour builder will not be triggered on edited messages
•
waitContent[Message] now require generic type. In case you wish to take any content or content message, you should use waitAnyContent[Message]GitHub
Release 5.2.1 · InsanusMokrassar/TelegramBotAPI
Core:
All the CallbackQueryes now will receive CommonUser instead of User due inability of bots to trigger any
inline interaction with others bots
API:
Now sentMessageFlow will take each sent m...
All the CallbackQueryes now will receive CommonUser instead of User due inability of bots to trigger any
inline interaction with others bots
API:
Now sentMessageFlow will take each sent m...
Hello everybody, 6.0.2 has been released, what happens since the 5.2.1 (and why not 6.0.0) :
• Kotlin 1.8.10 and other dependencies updates
• Update all
• Add opportunity to resend messages with
• Long polling have changed its base algorithm of media groups handling in updates. Since this update will be used the same mechanism as for webhooks - media groups will be delivered with debounce in 1 second (by default, configurable) due to the fact, that (for some reason) on the accounts created with virtual TON numbers media groups coming to the bot in different updates
• Kotlin 1.8.10 and other dependencies updates
• Update all
*.link extensions with renames according to their receivers to avoid collisions with link extensions of entities builder• Add opportunity to resend messages with
TelegramBot#resend extension (sending data as is instead of copy method)• Long polling have changed its base algorithm of media groups handling in updates. Since this update will be used the same mechanism as for webhooks - media groups will be delivered with debounce in 1 second (by default, configurable) due to the fact, that (for some reason) on the accounts created with virtual TON numbers media groups coming to the bot in different updates
GitHub
Release 6.0.2 · InsanusMokrassar/TelegramBotAPI
Core:
Long polling now uses media groups debounce as in webhooks
Long polling now uses media groups debounce as in webhooks
🎉1