Disabling Matrix Portalling
libera.chat
libera.chat
By now requiring users to go and contact chanops to ask them to explicitly plumb IRC channels to Matrix, it's just going to waste time for chanops, precipitate weird cross-plumbing failures, or fail outright (given plumbing channels with more than 100 users has to be done manually to prevent abuse).
It's very unfortunate that it's come to this, and I can only hope that the whole "opt in with a chanmode" thing happens, if portalling is off the table.
In fact, wouldn't it have been better to just ban the bridge by default, and let chanops unban it if they want people to be able to access via Matrix, rather than encourage people into the weird world of plumbing?
EDIT: clarifying that i'm not neutral on this, given i'm project lead for Matrix, and also responsible for running the Libera bridge at Element.
Matrix as a whole isn't banned, only the bridge operated by Element. If anything, this could encourage more people to run their own bridges (eg. Heisenbridge).
> while the bridge has certainly had problems over the years (e.g. occasional delays & a recent spate of dropped messages),
As well as flood (multiline messages and edits), spam, harassment[1], leaking secret channels[2], leaking past message metadata and channel membership.
[1]: https://twitter.com/AsahiLinux/status/1581103659013722112
[2]: https://github.com/matrix-org/matrix-appservice-irc/releases...
> it's also improved loads too
The very room used to discuss the Matrix bridge (#irc:matrix.org) has been dropping all IRC messages for at least three days, and the one to talk to Libera's staff (#libera-matrix:libera.chat) was only fixed today [EDIT: actually it's still dropping some people's messages]. The room used to discuss the Matrix spec (#spec:matrix.org) has been dropping them for over a year.
After two years of message drops, there is no way for users to know their messages are being dropped without using developer tools, causing miscommunication issues to many Free Software projects.
There have been, as far as I know, no work on addressing UX issues on the IRC side (primarily multiline messages, edits, and replies) in the last couple of years; except my work on MSC3968 and MSC3969 which is still awaiting initial review from Element four months after I submitted it.
That won't help 80% of the users that are not techy people. So yes imho while not intended as one, it will backfire as a full ban of matrix.
> except my work on MSC3968 and MSC3969 which is still awaiting initial review from Element four months after I submitted it.
Honestly, as a Matrix user, I hope these don't land any time soon as they will strongly decrease usability for matrix users. (And yes, I am going as far as saying that I want a native feeling chat on matrix side. Not an IRC emulation. If I wanted an IRC emulation, I would use an IRC client. That's EXACTLY the one thing I DO NOT want as a matrix user.)
There is an impedance mismatch between IRC and Matrix, and these try to find a middle-ground, by helping non-technical Matrix users follow social norms in a room they joined. As your own client dev, you are free not to implement these specs in your client to ignore these norms.
> [1]: https://twitter.com/AsahiLinux/status/1581103659013722112
What abuse? That link says "Matrix does not provide the moderation tools we need to keep our community safe", but doesn't say how their safety(?) was compromised.
I also find it odd since Mozilla switched from IRC to Matrix specifically because they wanted to censor people, I mean "keep our community safe" though "moderation tools".
https://discourse.mozilla.org/t/synchronous-messaging-at-moz...
Not sure, but here is what I can find in public logs:
https://oftc.irclog.whitequark.org/asahi/2022-10-12#31512149
https://oftc.irclog.whitequark.org/asahi/2022-10-13#31516958
https://oftc.irclog.whitequark.org/asahi/2022-10-14#31520624
https://oftc.irclog.whitequark.org/asahi/2022-10-14#31522316
> I also find it odd since Mozilla switched from IRC to Matrix specifically because they wanted to censor people, I mean "keep our community safe" though "moderation tools".
Mozilla had neglected their IRC network for years, so they were lacking the expertise. And they didn't try to reach out to other networks like Freenode (Libera Chat's predecessor) or OFTC to try to ask them for advice.
...is this sarcasm? I honestly can't tell
There's no need for hyperbole though. Libera overall only has a few tens of thousands of users, there's no way the vast majority are accessing it via Matrix like you say/imply. I'd wager we're less than 1000 impacted on libera.
Knowing that at least 1/4 of Libera users are from a fairly unstable bridge is really depressing. IRC truly is dying...
In terms of the bridge stability: there have obviously been stability problems over the last few months, but overall it's certainly been better than nothing. Agreed that the situation overall is really depressing.
That convenience is now going to be lost unless the IRC channel operators opt-in to create an account on Matrix, then set up a plumbed room on Matrix, and then advertise the plumbed rooms sufficiently well. Of course, many regular IRC users set up an IRC bouncer (I use ZNC myself) to keep a persistent connection to the IRC network, so this move would not affect them. But the portalled rooms served as a good alternative to setting up IRC bouncers yourself and unfortunately, this nice alternative is now going away.
As a channel moderator, I haven't been too happy with the plumbed channels either. For example, one of the things I have found to be a little problematic is that the Matrix bridge service joins the Matrix room with Admin power level. To avoid these complications, I wrote my own tiny script to bridge the Matrix rooms and IRC channels I needed. Since my script joins the networks as an ordinary client, it does not need elevated privileges in the channels/rooms. In case, anyone is interested in the script, I have shared it here: https://github.com/susam/nimb
The section "Differences from Matrix Appservice" at the bottom of the README in the preceding link explains some of the inconveniences I faced with the Matrix bridge service for plumbed channels and why I had to write my own script to avoid them.
I liked the bridge despite its occasional technical issues.
Matrix 2.0 is a step in the right direction, they better be serious about it (and to me that means not only mobile Element X, but also a new web app!).