-
Notifications
You must be signed in to change notification settings - Fork 30
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
Health check command? #24
Comments
The idea was that the protocol implementations do that automatically, thus that "connected" message in the status room. So this is more an issue of the specific protocol implementations, than the library. |
What is the 'relink' command meant to do? is that just an open command that each specific protocol puppet can decide what to use it for? |
@Sorunome I can move it to the IG protocol bridge, do you think it's better to add the command there or a general one like 'ping' mx-puppet-bridge? |
It'd be better if e.g. the IG bridge does that automatically in the background and then notifies the user about the status
Am 27. Januar 2020 22:00:50 MEZ schrieb Eric Migicovsky <[email protected]>:
…
@Sorunome I can move it to the IG protocol bridge, do you think it's
better to add the command there or a general one like 'ping'
mx-puppet-bridge?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#24 (comment)
|
The IG and Twitter bridges both seem to stop sending/receiving messages occasionally, silently without alerting user. Would it be possible for the bridge to routinely send a command in background (like get username) every few minutes? If it fails, restart the bridge?
The text was updated successfully, but these errors were encountered: