please warn that this project requires tdlib < 1.6.5

[3ynm]

It took me one day to compile tdlib on a SBC only to discover that the version I compiled is incompatible with this project.

[BenWiederhake]

Where would you put this warning? It's already there in CMakeLists.txt. If you find a good place, just make a PR.

[c0dev0id]

I'm currently looking into packaging tdlib-purple for OpenBSD. We have tdlib 1.7.7 already, which is required for the telegram cli client "tg". Now, before I start bundling tdlib 1.6.5 into the tdlib-purple port, I want to ask if tdlib-purple wants to support newer tdlibs in mid-term (aka someone is working on it) or if it's going to be stuck on 1.6.5 for the foreseeable future.

[BenWiederhake]

Want: Yes
someone is working on it: No
going to be stuck on 1.6.5 for the foreseeable future: Yes, probably … unless I can convince you to port it? :D

This might be a helpful starting point: #98
In particular, I hope it's really only a silly issue regarding either chat names, or some kind of ID that I misunderstood. The bug is probably in the diff, even, but I'm just too stupid.

[c0dev0id]

Hi Ben, thanks for the prompt response. This looks like more than wiping out a few incompatibilities. Thanks for the pointer to the diff.

EDIT: After reading tdlib/td#1718 (comment) it is clear to me that having tdlib around as independent library is not going to work anyway..

[ars3niy]

The thing with tdlib is that even minor versions can be incompatible in major ways. It's not really meant to be a system-wide shared library.

[mckaygerhard]

guys now take in consideration telegramdesktop/tdesktop#17330 telegram changes api now.. RPCError 406: UPDATE_APP_TO_LOGIN (caused by SignInRequest)

[ars3niy]

Now tdlib version requirement is >= 1.7.8 (no upper bound yet but there will be one as soon as tdlib changes something again). I suggest putting this in readme #126