Broken matrix bridge
I tried setting up a matrix client during the weekend. It looks like the IRC
to matrix bridge is broken.
e.g: messages sent on #opensuse-factory (IRC) are missing on
Probably related to this issue: https://github.com/matrix-org/matrix-appservice-irc/issues/1724
The bottom line of that issue seems to be that the IRC <-> Matrix bridge was patched to address the message dropping issue where some (many) messages weren't crossing the bridge. They deployed the patch about a month ago, but as many can see, it issue is alive and kicking!
Just to cross our T's and dot our I's. The bridge we run is Matrix <-> Discord/Telegram/Something-else?
Since Matrix clients can't really connect to IRC channels , whenever we go to e.g. #opensuse:libera.chat we are actually joining an IRC <-> Matrix bridged room. And Libera.chat's Matrix instance is run by Element nowadays .
Now, when we join #support:opensuse.org, we are joining an IRC <-> Matrix (or Matrix <-> IRC, whatever one's personal philosophy is) bridged room, but the Matrix instance is hosted by us instead. So, the ones that set up the bridge was the Libera.chat/Element folks, then? Based on Jacob's answer, it appears so and makes sense now that I face this fact.
- Fact picked up while lurking on #libera-matrix:libera-chat: https://matrix.to/#/!vjOdckstTLwMkKHIgz:libera.chat/$71uJNLMX01iFOBbYAVy5gcHmkgX3jffdAzxt7cYDtWU?via=matrix.org&via=libera.chat&via=mozilla.org
OK, after another round of digging I confirmed my previous beliefs, the bridged rooms in our instance (#foo:opensuse.org rooms) is set up by us , and makes more sense than my other statement.
But in the end, the bridge is the same (source code wise). So unless there's degraded performance with our homeserver (which is a reasonable assumption, since Synapse doesn't scale that well, to put it mildly), I'd say there won't be that much we can do, from our side, until the issue gets fixed upstream.
- Status changed from New to Closed
Since Libera.Chat asked Element to shutdown the Matrix<->IRC bridge because of issues like the one described here, among other things, we can close this ticket.
There's no real ETA for bringing back the bridge, though.