Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pull out API id and hash as runtime configurable parameters #129

Closed
wants to merge 1 commit into from
Closed

Pull out API id and hash as runtime configurable parameters #129

wants to merge 1 commit into from

Conversation

zer0def
Copy link

@zer0def zer0def commented Dec 7, 2021

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.

@ars3niy
Copy link
Owner

ars3niy commented Dec 7, 2021

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.

@zer0def
Copy link
Author

zer0def commented Dec 7, 2021

Do you mean "specify an alternate default API key" at compile time?

@ars3niy
Copy link
Owner

ars3niy commented Dec 7, 2021

Yes, a package built by me should use my personal API key at least by default.

@zer0def
Copy link
Author

zer0def commented Dec 7, 2021

Already adjusted the patch to cater to that use case.

@c0dev0id
Copy link

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.

@BenWiederhake
Copy link
Contributor

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

@zer0def zer0def closed this by deleting the head repository Feb 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants