RobustIRC v0.5 release

3 views
Skip to first unread message

Michael Stapelberg

unread,
Mar 30, 2017, 1:56:52 PM3/30/17
to robustirc-announce
Hey,

I’ve tagged the RobustIRC v0.5 release. Here are the release notes:

RobustIRC v0.5 (2017-03-30)

RobustIRC v0.5 contains the following changes:

• We switched to version 2 of sorcix/irc, which allows us to correctly interpret trailing and non-trailing IRC message parameters. This fixes issues with one-word messages in IRC clients such as Quassel, but might expose bugs in other programs/libraries. See this bugfix in an IRC bot.
• The ISON IRC command has been implemented.
• The PING IRC command is now ignored for idle time in WHOIS.
• The INVITE IRC command is now invalidated on JOIN.
• The WHOIS IRC command now results in RPL_WHOISREGNICK for identified users.
• The TOPIC IRC command now properly checks for operator status in +t channels.
• The user mode +i (invisible) has been implemented, dropping PRIVMSG and NOTICE IRC commands targetting you unless the sender shares a common channel with you.
• The irclog debug handler is now significantly faster (2m17s to 9s) due to using a bulk iterator.
• The configuration revision is now actually applied, protecting against conflicting edits.
• All mutex locks have been audited for correctness and a test has been added.
• TLS certificates/keys are now reloaded upon receiving a SIGHUP signal.
• When creating a channel, its modes now default to +nt.
• RobustIRC bridges can now be marked as trusted, resulting in the forwarded IP address being exposed. See issue #122 for details.
• The IRC channel mode +x has been implemented, requiring the user to solve a captcha before joining the channel.
• The CaptchaRequiredForLogin configuration option has been implemented, requiring users to solve a captcha before logging into the IRC network.
• The MaxSessions and MaxChannels configuration options have been implemented for limiting the maximum amount of memory.
• The GetMessage and session tables on the status pages are now sortable.
• The status pages now feature a quick way to kill sessions. Multiple sessions can be selected by holding the shift key.
• The status pages have been split into multiple subpages.
• At most one GetMessages request is now allowed per session per node.

Loadtesting the v0.5 RobustIRC release (with Go 1.8) showed that v0.5 can handle more than 2000 messages/s.
Reply all
Reply to author
Forward
0 new messages