tdlib-purple
tdlib-purple copied to clipboard
Pull out API id and hash as runtime configurable parameters
Ever since bumping tdlib-purple against tdlib>=1.7, users can experience 14:09 <@root> telegram-tdlib - Login error: Authentication error: code 400 (API_ID_PUBLISHED_FLOOD)
, which may necessitate them to generate their own API keys and recompile tdlib-purple with -DAPI_ID=<id> -DAPI_HASH=<hash>
.
This patch moves these parameters from being specified at compile time to run time.
But someone who builds and publishes packages (such as myself) must still be able to specify API key at compile time so that users won't have to.
Do you mean "specify an alternate default API key" at compile time?
Yes, a package built by me should use my personal API key at least by default.
Already adjusted the patch to cater to that use case.
Hello, I tested this PR and it works fine for me. I was able to enter the API information when adding the account in pidgin.
Hey everyone and especially zer0def, I've collected all open PRs into my master branch. I don't make any promises about keeping it up-to-date though.
https://github.com/BenWiederhake/tdlib-purple/#new-libpurple-plugin-for-telegram