Hello everybody :) there are two news:
* 24.0.1 has been released with small fix: now you may use common files with
* I have disabled stars on this channel. I did it because of channel got ~140⭐️ (~2$) since august of 24th and I even can't use it. So, I do not see any reason to left this way of some support - you will lose cents, I will not get anything :) In case you wish to support me or this library, you may donate to 🪙 TON wallet 💲 USDT (Tether network)
Have a nice day :)
* 24.0.1 has been released with small fix: now you may use common files with
EditChatMessageMedia/editMessageMedia* I have disabled stars on this channel. I did it because of channel got ~140
UQAtuSLJ76Zehc3qP-eRYMR98fPIu_oOp_atcpVX55zxHwTU or 0xF4032af0184F7Dc68a5b24A308F9Ad2BfD7be08FHave a nice day :)
Please open Telegram to view this post
VIEW IN TELEGRAM
GitHub
Release 24.0.1 · InsanusMokrassar/ktgbotapi
Core:
Now you may upload photos with EditChatMessageMedia
Now you may upload photos with EditChatMessageMedia
👍4
Hi :) it's happened, telegram team have launched Bots API 9.0. I haven’t seen an update that huge before, and I do not know when I will be able to correctly support it. The support of this update may be split into several releases. Anyway, I'll do my best to support new api asap!
Hope for your understanding, @InsanusMokrassar :)
Hope for your understanding, @InsanusMokrassar :)
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…
⚡3❤1
Kotlin Telegram Bot API Library (tgbotapi)
Hi :) it's happened, telegram team have launched Bots API 9.0. I haven’t seen an update that huge before, and I do not know when I will be able to correctly support it. The support of this update may be split into several releases. Anyway, I'll do my best…
Its been a month since I posted about Bot API 9.0 :) 25.0.0 reached test-ready phase :) if you want, you may try it with
25.0.0-rc, but I must warn you that this version is pretest one and I am sure it will have a lot of errors :)GitHub
25.0.0 by InsanusMokrassar · Pull Request #965 · InsanusMokrassar/ktgbotapi
Bot API 9.0
Business Accounts
Added the class BusinessBotRights and replaced the field can_reply with the field rights of the type BusinessBotRights in the class BusinessConnection.
Added the me...
Business Accounts
Added the class BusinessBotRights and replaced the field can_reply with the field rights of the type BusinessBotRights in the class BusinessConnection.
Added the me...
🔥3👍2
Forwarded from inmo.dev
Hello everybody. I have launched simple proxy https://proxy.nexus.inmo.dev for those who can't access direct https://nexus.inmo.dev . In case of some problems you may report me @InsanusMokrassar
Small remind about how to add my repository in groovy gradle:
Small remind about how to add my repository in groovy gradle:
repositories { // your dependencies repositories setup
mavenLocal() // typically enabled
mavenCentral() // typically enabled
google() // typically enabled
maven { url "https://nexus.inmo.dev/repository/maven-releases/" } // my repository, you may add `proxy` as mentioned above: `https://proxy.nexus.inmo.dev/repository/maven-releases/`
}🌚1
Hi :)
It's been 2 months since april 11th and now I want to notify you, that 26.0.0 with new bots API and dependencies updates has been released. Why this took this much time?
1. I have migrated onto new maven central publishing. First migration were as try to migrate onto OSSHR API, but it is too buggy, only then I found nmcp plugin ans have integrated new publicationin CI/CD process
2. Update contains mostly premium and/or stars features which a bit harder to test
3. In fact, there are 25.0.0, 25.0.1 and 25.0.2, but first two versions have been published with errors, last one have dependency on broken publication of MicroUtils
I hope on your understanding and wish you happy coding :)
It's been 2 months since april 11th and now I want to notify you, that 26.0.0 with new bots API and dependencies updates has been released. Why this took this much time?
1. I have migrated onto new maven central publishing. First migration were as try to migrate onto OSSHR API, but it is too buggy, only then I found nmcp plugin ans have integrated new publicationin CI/CD process
2. Update contains mostly premium and/or stars features which a bit harder to test
3. In fact, there are 25.0.0, 25.0.1 and 25.0.2, but first two versions have been published with errors, last one have dependency on broken publication of MicroUtils
I hope on your understanding and wish you happy coding :)
GitHub
Release 26.0.0 · InsanusMokrassar/ktgbotapi
THIS UPDATE CONTAINS BREAKING CHANGES IN BEHAVIOUR BUILDER AND CORE. BE CAREFUL ON UPDATE
Version:
Serialization: 1.8.0 -> 1.8.1
Coroutines: 1.10.1 -> 1.10.2
Ktor: 3.1.1 -> 3.1.3
MicroUt...
Version:
Serialization: 1.8.0 -> 1.8.1
Coroutines: 1.10.1 -> 1.10.2
Ktor: 3.1.1 -> 3.1.3
MicroUt...
❤3👍2🔥1
All technical sites will be down for several hours for technical works
Forwarded from inmo.dev
InsanusMokrassar/ktgbotapi: 26.1.0
GitHub
Release 26.1.0 · InsanusMokrassar/ktgbotapi
THIS UPDATE CONTAINS ADDING SUPPORT OF Telegram Bots API 9.1
THIS UPDATE MAY CONTAINS BREAKING CHANGES
THIS UPDATE MAY CONTAINS BREAKING CHANGES
🔥1
Hello everybody :) currently I am slowly working on 29.0.0 with new API implementation and API designers accepted as successful solution to add
For now I faced strange but important choice:
* To put both
* Add separated
direct_messages_topic_id which is 100% identical to message_thread_id but related to direct messages topics.For now I faced strange but important choice:
* To put both
message_thread_id and direct_messages_topic_id in send requests without modifying external API (which you are using in this library). There will be some probability that they will add topics in topics (topics in channels direct messages for each user) and it will require to make breaking changes. But for now it looks like some ugly and strange decision if they will make it* Add separated
directMessagesTopicId to be able to set it separately with messageThreadId (usually named as threadId). In that case it will be two different types which in fact are identical, but in code they will be partially-incompatibleGitHub
29.0.0 by InsanusMokrassar · Pull Request #998 · InsanusMokrassar/ktgbotapi
Checklists
Added the field checklist_task_id to the class ReplyParameters, allowing bots to reply to a specific checklist task.
Added the field reply_to_checklist_task_id to the class Message.
...
Added the field checklist_task_id to the class ReplyParameters, allowing bots to reply to a specific checklist task.
Added the field reply_to_checklist_task_id to the class Message.
...
What would you prefer?
Final Results
13%
Use `threadId` as common field to set both `message_thread_id` and `direct_messages_topic_id`
88%
Use separated `direct_messages_topic_id`