nimb VS modern-irc

Your security advisory has been quite helpful and I could reproduce the issue involving CR. It is particularly enlightening to know that the null byte could also cause the same issue because some IRC servers may interpret the null byte too as a line ending.

It is late here but I have pushed a quick fix to plug this loophole: <https://github.com/susam/nimb/commit/c5d6c4c>. Review comments, feedback, pull requests, patches, etc. are very welcome! This comment thread has been productive and constructive. Thank you!

Review comments, pull requests, feedback, etc. are welcome. T

I have had my own share of problems with both portalled rooms as well as plumbed rooms on Matrix. Dropped messages, dropped connections, etc. Sometimes the re-connection times can be several hours long. Despite these problems, the portalled rooms have been a convenient way for many IRC beginners to quickly set up a relatively persistent connection to the IRC network via the Matrix bridge. That convenience is now going to be lost unless the IRC channel operators opt-in to set up a plumbed room on Matrix and sufficiently advertise the plumbed rooms.

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 regular clients, it does not need elevated privileges in the channels/rooms. In case, anyone is interested in the script, I have it available 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.

You're not allowed null bytes in IRC messages: https://modern.ircdocs.horse/#parameters

Some IRC servers (especially those written in C) may interpret it as a line end, so you would have a similar issue

https://modern.ircdocs.horse/ is based on both 1459 and 2812, and describes the protocol shared by all current implementations. If you see any inaccuracy, please open a ticket at https://github.com/ircdocs/modern-irc/ so we can fix it.

You might wanna check it out. Things like code quotes and expand/collapse would be cool to add. I think some clients already support emoji as it's just UTF8?

It's common for IRC users to use IRC from a terminal client on their desktop. If they have a remote server, they'll use a screen session to keep their IRC client running in the background and re-open it when they want. Or they'll keep an eggdrop bot on a server somewhere, which is basically a sorta IRC proxy that they connect to from their desktop and can keep their user online in the background.

Here's some stuff on IRC: https://github.com/ircdocs/modern-irc | https://www.mirc.com/colors.html | https://wiki.wireshark.org/IRC