-
Notifications
You must be signed in to change notification settings - Fork 4
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
Log-in server (and plug-in) status #5
Comments
The useProxy flag in Session::connect should allow connecting to the numbered gateways. The 'xx' one was intended for 3rd party clients as I was once told, but I guess they dropped support for that. The pidgin plugin ought to have a checkbox for that somewhere in the settings. |
Thanks for that! In the account settings (Pidgin) I set the log-in server to |
I thought about this issue and concluded that this should be considered a bug because the default configuration is now broken. If you want I can put together a pull request that either changes the defaults or alters the README to instruct (new) users – or both. |
Hello, as you may have noticed, the log-in server at
g-xx.0.threema.ch
disappeared some time last fall. Are there any known alternatives? Or is this library (and purple/Pidgin plug-in) essentially dead without it?openMittsu is still working, so I’m trying to figure out what's going on.
From reading its source code, it looks like
xx
of the hostname should be replaced with digits. However, when I try that with a couple of values I only get an error message:They all point to the same two IP addresses 185.88.236.90 and 185.88.236.110, so I doubt that the specific digits matter.
The text was updated successfully, but these errors were encountered: