The most notable changes in this release are:
Fixed the Windows binary containing the wrong version in the main executable.
Relaxed validation of usernames in USER as it broke some clients.
Whitelisted the +channel-context tag in the ircv3_ctctags module.
No breaking configuration changes have been made since the v4.0.0 release. Please consult the list of breaking changes if you are upgrading from v3.
The full change log can be found on the docs site or on GitHub.
]]>The most notable changes in this release are:
Added extended ban d: (redirect) to the redirect module.
Added support for the IRCv3 ACCOUNTEXTBAN ISupport token.
Added support for the IRCv3 no-implicit-names specification to the ircv3 module.
Added support for the IRCv3 UTF8ONLY specification.
Added support for validating extended bans before they are set.
Added the sharebans module which allows bans to be shared between channels.
No breaking configuration changes have been made since the v4.0.0 release. Please consult the list of breaking changes if you are upgrading from v3.
The full change log can be found on the docs site or on GitHub.
]]>Modules and extensions being switched from reference<> and raw pointers to std::shared_ptr<>.
Unification of how module services (e.g. commands, modes, etc) are registered with the core.
A redesign of how IRC case-insensitive strings are hashed and compared to be more robust and work with newer C++ features like std::string_view.
A redesign of how server messages are built and emitted to allow future changes to the server protocol wire format.
Many modules with related behaviour (e.g. chg* and set*) being merged.
Many custom numerics and server notices being replaced with IRCv3 standard replies.
As you might imagine such large changes will need a lot of testing and we’re looking for volunteers to help out.
You help by running either v5.0.0dev3 or Git master, testing things which have changed, and reporting any bugs that you find. We are especially interested help with testing on systems other than glibc Linux.
If you can’t run your own network the InspIRCd Testnet is now running InspIRCd from Git master and has most modules loaded.
If you’re unable to help with testing you can also help by funding InspIRCd’s development. InspIRCd is currently maintained entirely by volunteers and every donation helps regardless of amount. For more information please visit our funding page.
]]>InspIRCd v5 is early in development. If you’d like to help out with development then please visit our development IRC channel.
]]>The most notable changes in this release are:
Added <autoconnect:bootperiod> to allow autoconnecting faster on first boot.
Changed the messageflood module to use a per-user flood counter.
Fixed being able to use expired or otherwise invalid client certificates in some circumstances.
Fixed channel mode f (flood) only blocking the first flood message.
Re-imported the regex_tre module now TRE is maintained again.
No breaking configuration changes have been made since the v4.0.0 release. Please consult the list of breaking changes if you are upgrading from v3.
The full change log can be found on the docs site or on GitHub.
]]>The most notable changes in this release are:
Added <sslprofile:securitylevel> to the ssl_openssl module for setting the OpenSSL security level.
Added an OpenRC init script to the scripts directory.
Added support for regex flags to the rline module.
Fixed enforcing the use of the Public Suffix List in link data.
Upgraded the Windows dependency system to use Conan 2.
No breaking configuration changes have been made since the v4.0.0 release. Please consult the list of breaking changes if you are upgrading from v3.
The full change log can be found on the docs site or on GitHub.
]]>The most notable changes in this release are:
Fixed a crash when a server operator with a custom connect class quits.
Added support for help channels in which users with user mode h (helpop) will be automatically granted a channel prefix mode.
Added the SAFERATE 005 token to allow modern clients (e.g. Soju) to know when fakelag is enabled and relax their internal message buffering.
Changed various messages to use long duration strings (e.g. “1 day, 2 hours, 3 minutes”) instead of short duration strings (e.g. 1d2h3m).
Improved the performance of formatting various messages.
No breaking configuration changes have been made since the v4.0.0 release. Please consult the list of breaking changes if you are upgrading from v3.
The full change log can be found on the docs site or on GitHub.
]]>The most notable changes in this release are:
Changed the /CBAN, /ELINE, /GLINE, /KLINE, /QLINE, /RLINE, and /ZLINE commands to make the duration field optional (defaults to permanent).
Fixed building the 005 numerics for users in removed connect classes.
Fixed finding the config file on portable installations (i.e. Windows).
Fixed removing regular bans that look like an extban.
Fixed TLS fingerprint fallback in SASL when using Atheme.
No breaking configuration changes have been made since the v4.0.0 release. Please consult the list of breaking changes if you are upgrading from v3.
The full change log can be found on the docs site or on GitHub.
]]>The most notable changes in this release are:
Added a “sslrehash” command to the helper script (requires the sslrehashsignal module).
Added support for explicitly disabling the ojoin and operprefix characters.
Fixed a crash from {fmt} when writing the pid file fails.
Fixed matching extended bans when multiple bans of a specific type are set.
Fixed stripping multiple formatting codes in a row.
No breaking configuration changes have been made since the v4.0.0 release. Please consult the list of breaking changes if you are upgrading from v3.
The full change log can be found on the docs site or on GitHub.
]]>The most notable changes in this release are:
Backported support for IRCv3 WebSocket subprotocols from the v4 branch.
Fixed hiding the server correctly when sending local chanlog messages.
Fixed the connectban module potentially generating a Z-line on a malformed CIDR range.
Fixed users not being removed from the services list when their server stops being a services server.
Updated the location of the InspIRCd IRC channels.
It is recommended that you consider upgrading to v4 as support for the v3 branch is planned to end on 2026-01-01. Please consult the v4 overview or the list of v4 breaking changes for more information about v4.
No breaking configuration changes have been made since the v3.0.0 release but if you are upgrading from v2 please consult our list of config changes in v3.
The full change log can be found on the docs site or on GitHub.
]]>