📣 The Release
We have updated our version of ProvisionIRCd, marking the culmination of an extensive period of testing and refinement. This release is primarily dedicated to addressing various bugs and bolstering performance, ensuring a smoother and more reliable experience for our users.
Additionally, we have introduced more ways for users to connect on other third-party platforms, and have introduced an additional network service to help those lock down their channels from any future and unwanted spambots from causing any issues.
👨💻 For Users
For the ProvisonIRCd upgrade, through the next few days, you may notice that various servers split, or are restarted in order to update the IRCd with these releases.
Some of the noticeable changes and bug fixes include the following below, split into each category.
Improvements
- Improvements to SSL connections include handling various handshakes better overall.
- Discord <-> IRC channel support has been introduced, please feel free to join on Discord to learn more: https://discord.gg/Akg5bv2GW4 - we are currently testing other connection-based services, and may update the Discord relay soon based on performance and overall benefits.
- LimitServ has been introduced that will handle channel limiting to prevent any spambots from mass joining. As of right now, this service is limited to network-owned channels but will be able to be invited by channel owners in a later release.
Bugfixes
- When a user would disconnect, sometimes there was a race connection where the IRCd would send them a request during the disconnect process resulting in unwanted conditions.
- We have fixed an issue with the webIRC protocol with Mibbit, which will work correctly and use the user’s own hostname vs. showing the default Mibbit hostname (and therefore limiting the number of active users on the web client at once).
⤴️ Contributions
If you run into any issues, please let us know or the developer by either commenting on the project ProvisionIRCd, by creating a new discussion under the tag Help > IRCd, or by joining our network help channel (#Help) and alerting the administration.
