Aliaksei Levin

It is definitely possible to achieve the same behavior in many ways. But is there reason to change the current implementation?

If you want the tags to identify "the versions that are recommended to be used", then you just need to use `master` branch with the latest TDLib version as you...

It is explained in the links that there is no "right time" for tags. Tag is just an alias for commit with some special meaning. If you need nothing special...

No, the tags are made on purpose. But as you should not use Telegram 2.5 (and you can't even download old app versions from any official distribution source), you should...

> At least it makes everyone aware of the changes. Any new commit makes everyone aware of the changes made to the project. > regular release has its uses You...

> users of apps that leverage tdlib on Void Linux will never have the most up to date version of the library. Each app version requires specific TDLib version and...

@stokito All TDLib versions are binary compatible when used with JSON interface, but you can never just replace TDLib with a different version without adjusting source code of the app...

Binaries aren't portable by definition and usually can be used only with specific OS version, so they will be hardly usable by real users. Also, TDLib supports many more operating...

Binary distributions are feasible for Windows and macOS, but not Linux because of too many mutually incompatible distros. Additionally, build process on Linux is very easy if binary portability isn't...

Messages with regular keyboards can't be edited, because the behavior of the keyboards depends on content of the messages.