Matrix<->IRC bridge issues
I'm an IRC user, and I noticed many issues about Appservice-IRC. This issue lists them all.
Long messages
Sometimes for some weird reason the following doesn't happen.
When a Matrix user sends a "long" message (e.g. multiline), it gets cropped and you get a link instead. For example, imagine that AwesomeMatrixUser
sends the following:
<AwesomeMatrixUser> Hi!
I got a very weird problem with pmaports. When I run `pmbootstrap init` it quits because of a syntax error..
Any hints?
I'd receive on IRC, this:
<AwesomeMatrixUser[m]> Hi!... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/(random_hash)>)
This is annoying. It forces me to open a web browser just to read this fairly short message. It's even worse when you have multiple people talking, but messages are "too long" for the bridge:
<MatrixUser1[m]> I think this... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/(random_hash)>)
<MatrixHaxxor[m]> No, you're... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/(random_hash)>)
<someone_hi[m]> Why are you sending so much long messages?... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/(random_hash)>)
Ironically the link is longer than the "preview".
See: https://github.com/matrix-org/matrix-appservice-irc/issues/701
Edits
IRC doesn't support edits, the workaround EMS decided to go with is resending the full edited message. For example, AwesomeMatrixUser
sends the following message:
<AwesomeMatrixUser> I took a backap of my /etc/apk/warld and copied it to my hame directory
And then realises they've misspelled world
as warld
, home
as hame
and backup
as backap
. They edit their message accordinately twice. This is what they see now:
<AwesomeMatrixUser (edited)> I took a backup of my /etc/apk/world and copied it to my home directory
But this is what I see:
<AwesomeMatrixUser[m]> I took a backap of my /etc/apk/warld and copied it to my hame directory
<AwesomeMatrixUser[m]> * I took a backup of my /etc/apk/world and copied it to my hame directory
<AwesomeMatrixUser[m]> * I took a backup of my /etc/apk/world and copied it to my home directory
This looks very spammy on the IRC side. What I'd expect seeing is this:
<AwesomeMatrixUser[m]> I took a backap of my /etc/apk/warld and copied it to my hame directory
<AwesomeMatrixUser[m]> s/backap/backup/ s/warld/world/
<AwesomeMatrixUser[m]> s/hame/home/
Or:
<AwesomeMatrixUser[m]> *backup, *world
<AwesomeMatrixUser[m]> *home
Small code blocks
When I say small code blocks, I mean this
. Let's say AwesomeMatrixUser
sends this:
<AwesomeMatrixUser> Just ran `sudo` and it hangs...
I get this:
<AwesomeMatrixUser[m]> Just ran ^Qsudo and it hangs...
+q mode
When setting +q to a user, this effectively makes them unable to talk; but if you set it to a Matrix user, they'll still be able to talk, just not in the IRC channel but other Matrix users will still see messages.
Other issues
- Coloured messages on Matrix appear as uncoloured on IRC: ideally translate the HTML into colour codes
- Paste/Upload links for images or pasted code blocks are way too long
- Replying to your own message makes you ping yourself on IRC (
<AwesomeMatrixUser[m]> AwesomeMatrixUser[m]: reply to my own message
): ideally use<AwesomeMatrixUser[m]> <AwesomeMatrixUser[m]> "message..." <- reply to my own message
format - Apparently silently drops messages and leaks the existence of secret
+s
channels (see https://libera.chat/news/matrix-irc-bridge-updates) - ...
I think we should try finding a better bridge, because most of these issues got reported a long time ago and never got solved. Tell me your thoughts below...
Edit:
**
Messages getting silently dropped and mass quits
This issue is happening very often. Sometimes all matrix puppets quit, then many messages sent are simply not getting bridged to IRC. For example as of now (01/12/2023, 14:55 UTC) longnoserob, hacker420 and рейму хакуреевский's messages are getting silently dropped on IRC side. This is so far the biggest issue of the bridge.
Apparently this has been known for years, but nobody is working on addressing this critical issue (which is one of the reasons why the libera.chat bridge got shut down) **