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
{{ message }}
This repository has been archived by the owner on Oct 24, 2018. It is now read-only.
Messages can end up going to an empty room (that may no longer be joinable) because synapse doesn't clean up aliases, and likewise telematrix doesn't either.
Steps to reproduce the problem:
Set up a bridge to a room
Kick everyone and force them to leave, making the room invite only in the process
Leave the room yourself
Set up the bridge in a new room (and get the "alias already in use" error)
As a server admin, delete the room alias from the directory
Set up the bridge in your new room (that failed just a couple steps ago)
Try sending messages from telegram
What ends up happening is the old link is kept in telematrix, making it so the bridge tries to send to the old room instead of the new room. The new room is recorded in the table though.
There's a few options to handle this:
Send events from telegram to all linked matrix rooms (or try to, making sure not to fail on all rooms if one is invite only)
If there are duplicates, or doubts that the alias is correctly mapped (ie: room not joinable), then query the homeserver for an updated room ID
Always send events to the last linked matrix room instead of the first
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Messages can end up going to an empty room (that may no longer be joinable) because synapse doesn't clean up aliases, and likewise telematrix doesn't either.
Steps to reproduce the problem:
What ends up happening is the old link is kept in telematrix, making it so the bridge tries to send to the old room instead of the new room. The new room is recorded in the table though.
There's a few options to handle this:
The text was updated successfully, but these errors were encountered: