diff options
| -rw-r--r-- | NEWS | 48 |
1 files changed, 48 insertions, 0 deletions
@@ -0,0 +1,48 @@ +blabouncer 0.2 - 2019-09-16 + + New features: + - Implement arrays in the configuration file and use them to specify: + - multiple connect commands + - multiple nicks + - Add a configuration file option to include the date in the timestamp when + replaying the replay log. + - Please note: the above two configuration file changes require changes to the + configuration file, please see blabouncer.conf.example. + - Log server messages to a file named <ircdname>.log. + - Log additional things in channel log files: + - QUIT messages + - NICK changes + - Channel/user MODEs + + Changes: + - BLABOUNCER REPLAY time is now specified with D:H:M instead of D:H:M:S. + - Send remote IP addresses instead of fd numbers in NOTICEs to clients. + - Make some older compilers happy by specifying -D_BSD_SOURCE and -std=gnu99. + - Make all log filenames lowercase - since IRC nicks and channel names are + case-insensitive, we can ensure a nick/channel with varying case always ends + up in the same log file. Please note this may mean any existing log files + with uppercase letters will no longer be written to. + + Bug fixes: + - Avoid various cases of server responses being relayed to all clients instead + just the requesting client. + - Avoid non-existent users appearing in channels after they change nicks by + replay logging nick changes. + - Avoid NICK synchronisation issues by ignoring replay log nick changes from + us if not our current nick, and by completely ignoring replaying any type of + replay log line from before blabouncer was launched. + - Avoid possible crash if replay file does not exist. + - Avoid possible crash if a socket write fails. + - Many, many, more! + + +blabouncer 0.1.1 - 2019-07-25 + + Bug fixes: + - Fix logging to the wrong file in the case that the bouncer's nick changed + whilst running. + + +blabouncer 0.1 - 2019-07-18 + + - Initial release. |