You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I understand, the appservice bot (the one that sits in IRC, if enabled in the config.yaml) is really only useful for when there are no matrix-side users in the room, to hear the messages and keep them synced on the homeserver.
When the bot is disabled, it will use the matrix-users for that.
When the bot is enabled, it actually is single-point-of-failure with a non-obvious failure state, simply by being kicked. And does not self-heal (retry join).
The text was updated successfully, but these errors were encountered:
When in bot-only mode, the bot does not attempt to re-join after being kicked by design, to avoid pissing off IRC users with obnoxious auto-rejoining bots. It could send a message to the corresponding Matrix room however.
kegsay
changed the title
Bot user, when kicked, does not rejoin or notify of a problem
If the bot user is kicked from IRC, it should notify the mapped Matrix rooms about it
Apr 18, 2017
From what I understand, the appservice bot (the one that sits in IRC, if enabled in the config.yaml) is really only useful for when there are no matrix-side users in the room, to hear the messages and keep them synced on the homeserver.
When the bot is disabled, it will use the matrix-users for that.
When the bot is enabled, it actually is single-point-of-failure with a non-obvious failure state, simply by being kicked. And does not self-heal (retry join).
The text was updated successfully, but these errors were encountered: