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
Kotlin Telegram Bot API Library (tgbotapi)
Photo
So, that is happen 🎉 ktgbotapi 9.3.0 has been released. What is here:

• Kotlin 1.9.20 🎉
• Minimal JDK 17 😔
• Other libraries update
• ABSOLUTELY experimental armX64 support (require some ktor client due to tls support absence in cio)

This update become possible thanks to Anton Lakotka
👍2
Hello everybody :) as some of you know, I am developing KSLog library. It is easy-to-use and lightweight logging library. Also you could face println in your app: Warning!!! Other bot with the same bot token requests updates with getUpdate in parallel. It is just common println which can't be managed in any way, it will be printed in console unconditionally in case when your bot is running in parallel mode. So, there is suggestion to include KSLog in standard dependency of ktgbotapi and make some workaround for logs setting up.
Hello everybody. I wished to notify you that 9.4.1 do not compatible with MicroUtils 0.20.23 due to migration of name IetfLanguageCode and all subsequent functions onto IetfLang. Currently, I am preparing migration version with compatibility changes
Hello everybody :)

As you may know, telegram bots api 7.0 has been released. Due to a lot of changes in API, I have started 10.0.0 version of the library and I will be glad to your suggestions about some new features in this update as always :)
👍1
Hi again :) Unfortunatelly, new year is coming, and several days I will be unable to update library up to new API :( it is about work

I wish you all had nice year or, at least, not bad. Nobody knows, what will this year bring, but is should be interesting. I hope you all will create new goals due to achievement of the exists one in this or new year :)

Happy new year🎉🎉🎉
🎉6
So slow :( as I expected, this update is very huge. In case you wish to use development version with currently covered API, you may look into my nexus with development builds (labeled with build number). I plan to continue to cover new API as fast as I can, but can't guarantee when it will be release 😔
🔥21
Hello everybody :) about the progress in two words: all API has been covered and I have updated examples to be successfuly built with new version of library. In case you wish, you may try to test new API in examples and any issues and errors to me here
3🔥1
Hello everybody :) I glad to announce that ktgbotapi 10.0.0 has been released ❤️ (as well as update in examples project 😏)

First of all, THIS UPDATE CONTAINS A LOT OF BREAKING CHANGES:

• Using of com.soywiz.korge:korlibs-time and com.soywiz.korge:korlibs-crypto instead old one packages. It will not lead to code problems (but you may require to add imports of `millisecondsLong`), but you will need to update your dependencies in case they are used directly
Message has been renamed to AccessibleMessage. You still may use Message interface, but it is common interface for both AccessibleMessage and InaccessibleMessage.
• In most places disableWebPagePreview has been replaced by new LinkPreviewOptions
• In most places arguments replyToMessageId and allowSendingWithoutReply has been replaced with ReplyParameters
• In reply extensions two parameters have been added: replyInChatId and replyInThreadId

Of course, this update also contains API changes related to Telegram Bots API 7.0

With all problems you always may me write me in PM or in our group and forum

Have a nice update and new year :)
4🥰1🎉1
As always, hi :) Telegram Bots API has been updated up to version 7.1 and I am working to bring the support of this update in lib. Currently it looks like I need to test it and make some fixes (possibly). You may suggest some of your thoughts about improvement of library and they can be included in coming 10.1.0 update :)
🔥1🌚1
Long time no see, hi :) From one of users I got suggestion to rewrite all typealiases (like MessageId) as value classes. It is breaking with two sides of consequences:

+ We will be able to work with the same data under the hood by more strong-typed way. It seems that it will be harder to missuse types (like pass file id instead of query id)
- Update with this content may totally break your code, because you will need to use constructors instead of raw data
Hello everybody :) I am starting review and integration of new API into library. It will be major update, so, you may suggest some breaking changes and there is high chance to see them in this release

P.S. Unfortunatelly, I can't guarantee that update will be released near time, but I will try hard to complete it asap
1