99d5b5b9a9
UnrealIRCd 5.0.3.1 ------------------- This fixes a crash issue after REHASH in 5.0.3. UnrealIRCd 5.0.3 ----------------- Fixes: * Fix serious flood issue in labeled-response implementation. * An IRCOp SQUIT'ing a far remote server may cause a broken link topology * In channels that are +D (delayed join), PARTs were not shown correctly to channel operators. Enhancements: * A new HISTORY command for history playback (```HISTORY #channel number-of-lines```) which allows you to fetch more lines than the on-join history playback. Of course, taking into account the set limits in the +H channel mode. This command is one of the [two interfaces](https://www.unrealircd.org/docs/Channel_history#Ways_to_retrieve_history) to [Channel history](https://www.unrealircd.org/docs/Channel_history). * Two new [message tags](https://www.unrealircd.org/docs/Message_tags), ```unrealircd.org/userip``` and ```unrealircd.org/userhost``` which communicate the user@ip and real user@host to IRCOps. Changes: * Drop the draft/ prefix now that the IRCv3 [labeled-response](https://ircv3.net/specs/extensions/labeled-response.html) specification is out of draft. * The operclass permission ```immune:target-limit``` is now called ```immune:max-concurrent-conversations```, since it bypasses [set::anti-flood::max-concurrent-conversations](https://www.unrealircd.org/docs/Set_block#set::anti-flood::max-concurrent-conversations). For 99% of the users this change is not important, but it may be if you use highly customized [operclass blocks](https://www.unrealircd.org/docs/Operclass_block) Are you upgrading from UnrealIRCd 4.x to UnrealIRCd 5? If so, then check out the *UnrealIRCd 5* release notes [further down](#unrealircd-5). At the very least, check out [Upgrading from 4.x](https://www.unrealircd.org/docs/Upgrading_from_4.x). |
||
---|---|---|
.. | ||
files | ||
patches | ||
DESCR | ||
distinfo | ||
Makefile | ||
options.mk | ||
PLIST |