A modern IRC server (daemon/ircd) written in Go.
We're pleased to be publishing the release candidate for 2.6.0 (the official release should follow in a week or so).
This release has some user-facing enhancements, but is primarily focused on fixing bugs and advancing the state of IRCv3 standardization (by publishing a release that implements the latest drafts). Some highlights:
+B in our implementation) (#1562)This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading.
This release includes no changes to the embedded database format. If you are using MySQL for history storage, it adds a new table; this change is backwards and forwards-compatible and does not require any manual intervention.
If you are using nginx as a reverse proxy for IRC-over-websockets, previous documentation did not recommend increasing proxy_read_timeout; the default value of 60s is too low and can lead to user disconnections. The current recommended value is proxy_read_timeout 600s;; see the manual for an example configuration.
Many thanks to @ajaspers and @Mikaela for contributing patches, to @aster1sk, @emersion, @eskimo, @hhirtz, @jlu5, @jwheare, @KoraggKnightWolf, @kylef, @Mikaela, @mogad0n, @ProgVal, and @szlend for reporting issues and helping test, and to our translators for contributing translations.
server.compatibility.allow-truncation, controlling whether the server accepts messages that are too long to be relayed intact; this value defaults to true when unset (#1596, thanks @kylef!)snomasks operator capability; operators must have either the ban or snomasks capability to subscribe to additional snomasks (#1176)UTF8ONLY guarantee, or to a text-mode websocket client (#1575, #1596, thanks @ProgVal!)UBAN now produces snomasks and audit loglines (#1518, thanks @mogad0n!)draft/register specification (#1568, thanks @ProgVal!)433 ERR_NICKNAMEINUSE is no longer sent when a fully connected ("registered") client fails to claim a reserved nickname, fixing a bad interaction with some client software (#1594, thanks @ProgVal!)znc.in/playback commands causing client disconnections when history is disabled (#1552, thanks @szlend!)696 ERR_INVALIDMODEPARAM response for invalid channel keys (#1563, thanks @ProgVal!)CS TRANSFER error messages (#1534, thanks burning!)/LIST output, even with no members (#1507)server.compatibility.allow-truncation; this field defaults to true when unset, preserving the legacy behavior for older config files (#1577, #1586, thanks @kylef!)+R registered-only usermode now produce an error message (#1064, thanks @KoraggKnightWolf, @ajaspers!)CS OP will regrant your channel AMODE, in case you removed it (#1516, #1307, thanks @jlu5!): (#1571)CS AMODE and NS UNREGISTER (#1524, #1545, thanks @Mikaela!)WARN NICK ACCOUNT_REQUIRED is sent on failed attempts to claim a reserved nickname (#1594)NS CLIENTS LIST displays enabled client capabilities (#1576)CS INFO with no arguments lists your registered channels (#765)NS PASSWORD is now accepted as an alias for NS PASSWD (#1547)Oragono 2.5.1 is a bugfix release that fixes a significant security issue. We apologize for the oversight.
This release includes no changes to the config file format or the database.
Many thanks to @xnaas for reporting the issue.
We're pleased to announce Oragono 2.5.0, a new stable release.
This release includes enhancements based on the needs of real-world operators, as well as bug fixes. Highlights include:
UBAN, a new "unified ban" system for server operators, with a corresponding CHANSERV HOWTOBAN command for channel operators (#1447)+f (#1260)This release includes changes to the config file format, including two breaking changes. One is fairly significant: enabling a websocket listener now requires the use of server.enforce-utf8, as has been the recommended default since 2.2.0 (so continuing to accept legacy non-UTF-8 content will require disabling websockets). The other is that the "unban" operator capability has been removed (it is now included in the "ban" capability). Other config changes are backwards compatible and do not require updating the file before upgrading.
This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).
Many thanks to @jlu5, @kylef and @Mikaela for contributing patches, to @bogdomania, @eskimo, @happyhater, @jlu5, @kylef, @LukeHoersten, @Mikaela, @mogad0n, @robinlemon, and @vertisan for reporting issues and helping test, and to our translators for contributing translations.
server.enforce-utf8 = true (#1483)proxy is now a top-level field of the listener config block; in particular, the PROXY protocol (v1 or v2) can now be required ahead of a plaintext connection. The field is still accepted in its legacy position (inside the tls block). (#1389, thanks @robinlemon!)accounts.multiclient.always-on-expiration, allowing always-on clients to be timed out for inactivity (#810, thanks @bogdomania!)local_ prefixes have been stripped from operator capability names, so that, e.g., local_ban is now just ban. The old names are still accepted. (#1442)local_unban operator capability has been removed (unbanning is now contained in the ban permission). (#1442)accounts.bcrypt-cost is now 4, the minimum acceptable value (#1497)server.ip-limits.custom-limits now accepts networks that contain multiple CIDRs; the old syntax is still accepted (#1421, thanks @Mikaela!history.restrictions.query-cutoff, generalizes the old history.restrictions.enforce-registration-date (the old field is still accepted) (#1490, thanks @Mikaela!)server.override-services-hostname, allowing the hostname of NickServ, ChanServ, etc. to be overridden (#1407, thanks @Mikaela!)hide-sts key to the listener block; this can be used to hide the STS CAP when the listener is secured at layer 3 or 4 (e.g., by a VPN or an E2E mixnet). It will still be necessary to add the relevant IPs to secure-nets. (#1428, thanks @Mikaela!)DEFCON 4 and lower now require Tor users to authenticate with SASL (#1450)NS UNSUSPEND requiring the casefolded / lowercase version of the account name (#1382, thanks @mogad0n!)PRIVMSG not being replayed (#1411)RENAME (i.e., channel rename) (#1456, thanks @mogad0n!)KLINE response (#1379, thanks @mogad0n!)RELAYMSG tag name is now draft/relaymsg, conforming to the amended draft specification (#1468, thanks @jlu5!)SAJOIN not sending a MODE line to the originating client (#1383, thanks @mogad0n!)CS AMODE (#1383, thanks @mogad0n!)JOIN line sent to some clients using the draft/resume-0.5 extension (#1397, thanks @kylef!)+o, +v) of always-on clients are now persisted in the database (#1345)/CHANSERV PURGE now takes ADD, DEL, and LIST subcommands; the separate UNPURGE command has been removed; PURGE ADD now requires a confirmation code (#1294, thanks @mogad0n!)<, >, ', ", and ; are no longer allowed in nicknames (previously registered account names containing these characters are still accepted) (#1436, thanks @happyhater!)*!*@tor-network.onion (#1479, thanks @mogad0n!)001 RPL_WELCOME (#1410)RELAYMSG can now take client-only tags (#1470)text.ircv3.net subprotocol; negotiating this is optional for clients (#1483)UBAN, a new command giving server operators a unified interface to D-LINEs (IP bans), K-LINEs (NUH mask bans, which are now deprecated), and account suspensions (NS SUSPEND) (#1447)CHANSERV HOWTOBAN, a ChanServ subcommand that helps channel operators choose an appropriate ban (#1447)+f; users who cannot join the channel due to +i or +l will be forwarded to the channel specified by +f. (#1260)/JOIN 0 (part all channels), requiring a confirmation code (#1417, thanks @Mikaela!)INVITE (#1409, thanks @Mikaela!)/CS SET: history-cutoff, allowing the channel owner more fine-grained control over who can see history (#1490, thanks @Mikaela!)UTF8ONLY ISUPPORT token, allowing the server to advertise to clients that only UTF-8 content is accepted (#1483)/NICKSERV RENAME, an operator-only command that can change the case of an account name (#1380, thanks @LukeHoersten!)We're pleased to be publishing the release candidate for 2.5.0 (the official release should follow in a week or so).
This release includes enhancements based on the needs of real-world operators, as well as bug fixes. Highlights include:
UBAN, a new "unified ban" system for server operators, with a corresponding CHANSERV HOWTOBAN command for channel operators (#1447)+f (#1260)This release includes changes to the config file format, including two breaking changes. One is fairly significant: enabling a websocket listener now requires the use of server.enforce-utf8, as has been the recommended default since 2.2.0 (so continuing to accept legacy non-UTF-8 content will require disabling websockets). The other is that the "unban" operator capability has been removed (it is now included in the "ban" capability). Other config changes are backwards compatible and do not require updating the file before upgrading.
This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).
Many thanks to @jlu5, @kylef and @Mikaela for contributing patches, to @bogdomania, @eskimo, @happyhater, @jlu5, @kylef, @LukeHoersten, @Mikaela, @mogad0n, @robinlemon, and @vertisan for reporting issues and helping test, and to our translators for contributing translations.
server.enforce-utf8 = true (#1483)proxy is now a top-level field of the listener config block; in particular, the PROXY protocol (v1 or v2) can now be required ahead of a plaintext connection. The field is still accepted in its legacy position (inside the tls block). (#1389, thanks @robinlemon!)accounts.multiclient.always-on-expiration, allowing always-on clients to be timed out for inactivity (#810, thanks @bogdomania!)local_ prefixes have been stripped from operator capability names, so that, e.g., local_ban is now just ban. The old names are still accepted. (#1442)local_unban operator capability has been removed (unbanning is now contained in the ban permission). (#1442)accounts.bcrypt-cost is now 4, the minimum acceptable value (#1497)server.ip-limits.custom-limits now accepts networks that contain multiple CIDRs; the old syntax is still accepted (#1421, thanks @Mikaela!history.restrictions.query-cutoff, generalizes the old history.restrictions.enforce-registration-date (the old field is still accepted) (#1490, thanks @Mikaela!)server.override-services-hostname, allowing the hostname of NickServ, ChanServ, etc. to be overridden (#1407, thanks @Mikaela!)hide-sts key to the listener block; this can be used to hide the STS CAP when the listener is secured at layer 3 or 4 (e.g., by a VPN or an E2E mixnet). It will still be necessary to add the relevant IPs to secure-nets. (#1428, thanks @Mikaela!)DEFCON 4 and lower now require Tor users to authenticate with SASL (#1450)NS UNSUSPEND requiring the casefolded / lowercase version of the account name (#1382, thanks @mogad0n!)PRIVMSG not being replayed (#1411)RENAME (i.e., channel rename) (#1456, thanks @mogad0n!)KLINE response (#1379, thanks @mogad0n!)RELAYMSG tag name is now draft/relaymsg, conforming to the amended draft specification (#1468, thanks @jlu5!)SAJOIN not sending a MODE line to the originating client (#1383, thanks @mogad0n!)CS AMODE (#1383, thanks @mogad0n!)JOIN line sent to some clients using the draft/resume-0.5 extension (#1397, thanks @kylef!)+o, +v) of always-on clients are now persisted in the database (#1345)/CHANSERV PURGE now takes ADD, DEL, and LIST subcommands; the separate UNPURGE command has been removed; PURGE ADD now requires a confirmation code (#1294, thanks @mogad0n!)<, >, ', ", and ; are no longer allowed in nicknames (previously registered account names containing these characters are still accepted) (#1436, thanks @happyhater!)*!*@tor-network.onion (#1479, thanks @mogad0n!)001 RPL_WELCOME (#1410)RELAYMSG can now take client-only tags (#1470)text.ircv3.net subprotocol; negotiating this is optional for clients (#1483)UBAN, a new command giving server operators a unified interface to D-LINEs (IP bans), K-LINEs (NUH mask bans, which are now deprecated), and account suspensions (NS SUSPEND) (#1447)CHANSERV HOWTOBAN, a ChanServ subcommand that helps channel operators choose an appropriate ban (#1447)+f; users who cannot join the channel due to +i or +l will be forwarded to the channel specified by +f. (#1260)/JOIN 0 (part all channels), requiring a confirmation code (#1417, thanks @Mikaela!)INVITE (#1409, thanks @Mikaela!)/CS SET: history-cutoff, allowing the channel owner more fine-grained control over who can see history (#1490, thanks @Mikaela!)UTF8ONLY ISUPPORT token, allowing the server to advertise to clients that only UTF-8 content is accepted (#1483)/NICKSERV RENAME, an operator-only command that can change the case of an account name (#1380, thanks @LukeHoersten!)We're pleased to announce Oragono 2.4.0, a new stable release.
This release includes a number of exciting enhancements and fixes. Here are some highlights:
+u ("auditorium", #1300), +U ("op-moderated", #1178), +M ("moderated-registered", #1182, thanks @ajaspers!), and +b m: (an extban for muting users, #307)This release includes changes to the config file format, including one breaking change: roleplay.enabled now defaults to false (the new recommended default) instead of true when unset. Other config changes are backwards compatible and do not require updating the file before upgrading.
This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).
Many thanks to @ajaspers, @jesopo, @moortens, and @RunBarryRun for contributing patches, to @csmith for contributing code reviews, to @ajaspers, @Amiga60077, @bogdomania, @csmith, @edk0, @eskimo, @jlu5, @jwheare, @KoraggKnightWolf, @Mitaka8, @mogad0n, @RyanSquared, and @vertisan for reporting issues and helping test, and to our translators for contributing translations.
server.ip-cloaking.enabled-for-always-on, which generates a unique hostname for each always-on client. The recommended default value of this field is true (#1312)server.coerce-ident; if this is set to a string value, all user/ident fields supplied by clients are ignored and replaced with this value. The recommended default value of this field is ~u. This simplifies bans. (#1340)accounts.nick-reservation.email-verification section. The old format (callbacks) is still accepted (#1075)roleplay.enabled is now false; this field now defaults to false when unset (#1240, #1271)server.relaymsg section for configuring the new draft/relaymsg capability; added the new relaymsg operator capability for exercising it (#1119)allow-environment-overrides config variable, allowing config options to be overridden by environment variables. See the manual for more details. (#1049, thanks @csmith!)server.ip-check-script for configuring IP check plugins (#68, #1267, thanks @moortens!)max-concurrency restriction to accounts.auth-script section. The recommended default value is 64 (0 or unset disable the restriction) (#1267)accounts.registration.allow-before-connect; this allows the use of the new REGISTER command before connecting to the server (#1075)hidden option in operator blocks: if set to true, operator status is hidden from commands like WHOIS that would otherwise display it (#1194)accounts.nick-reservation.forbid-anonymous-nick-changes, which forbids anonymous users from changing their nicknames after initially connecting (#1337, thanks @Amiga60077!)channels.invite-expiration, allowing invites to +i channels to expire after a given amount of time (#1171)/NICKSERV CLIENTS LOGOUT command for disconnecting clients connected to a user account (#1072, #1272, thanks @ajaspers!)INVITE for invite-only channels, including an UNINVITE command (#1171)REQUEST, APPROVE, and REJECT subcommands of HOSTSERV (#1346)PONG is now sent with the server name as the first parameter, matching the behavior of other ircds (#1249, thanks @jesopo!)+T no-CTCP user mode; this has been fixed (#1299, thanks @mogad0n!)/NICKSERV SAREGISTER of confusable nicknames (#1322, thanks @mogad0n!)LUSERS counts caused by KLINE (#1303, thanks @mogad0n!)CHATHISTORY queries for invalid channels now get an empty batch instead of a FAIL (#1322)fakelag.messages-per-window = 0 no longer causes a panic (#861, thanks @vertisan!)oragono importdb command for importing a converted Anope or Atheme database; see the manual for details (#1042)ip-check-script, a scripting API for restricting access by client IP. We provide oragono-dnsbl, an external script that can query DNSBLs for this purpose (#68, #1267, thanks @moortens!)+u. This is an "auditorium" mode that prevents unprivileged users from seeing each other's JOIN and PART lines. It's useful for large public-announcement channels, possibly in conjunction with +m (#1300)+U. This is an "op-moderated" mode; messages from unprivileged users are sent only to channel operators, who can then choose to grant them +v. (#1178)+b m:: users matching the ban expression (e.g., +b m:*!*@j6dwi4vacx47y.irc) will be able to join the channel, but will be unable to speak. (#307)379 RPL_WHOISMODES line to the WHOIS response, making it easier for operators to see other users' modes (#769, thanks @Amiga60077 and @KoraggKnightWolf!)/CHANSERV DEOP command for removing channel operator privileges (#361, thanks @RunBarryRun!)r flag to /WHO responses for registered nicknames (#1366, thanks @Amiga60077!)~u by default, instead of ~user; this can be changed by setting the coerce-ident field (#1340)/NICKSERV SUSPEND has been modified to take subcommands (ADD, DEL, and LIST); the ADD subcommand now accepts time duration and reason arguments. See /msg NickServ HELP SUSPEND for details. (#1274, thanks @mogad0n!)/NICKSERV SESSIONS is now /NICKSERV CLIENTS LIST, but the old command is still accepted (#1272, thanks @ajaspers!)SETNAME behavior for legacy clients (#1358, thanks @KoraggKnightWolf!)conventional.yaml to traditional.yaml (#1350)We're pleased to be publishing the release candidate for 2.4.0 (the official release should follow in a week or so).
This release includes a number of exciting enhancements and fixes. Here are some highlights:
+u ("auditorium", #1300), +U ("op-moderated", #1178), +M ("moderated-registered", #1182, thanks @ajaspers!), and +b m: (an extban for muting users, #307)This release includes changes to the config file format, including one breaking change: roleplay.enabled now defaults to false (the new recommended default) instead of true when unset. Other config changes are backwards compatible and do not require updating the file before upgrading.
This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).
Many thanks to @ajaspers, @jesopo, @moortens, and @RunBarryRun for contributing patches, to @csmith for contributing code reviews, to @ajaspers, @Amiga60077, @bogdomania, @csmith, @edk0, @eskimo, @jlu5, @jwheare, @KoraggKnightWolf, @Mitaka8, @mogad0n, @RyanSquared, and @vertisan for reporting issues and helping test, and to our translators for contributing translations.
server.ip-cloaking.enabled-for-always-on, which generates a unique hostname for each always-on client. The recommended default value of this field is true (#1312)server.coerce-ident; if this is set to a string value, all user/ident fields supplied by clients are ignored and replaced with this value. The recommended default value of this field is ~u. This simplifies bans. (#1340)accounts.nick-reservation.email-verification section. The old format (callbacks) is still accepted (#1075)roleplay.enabled is now false; this field now defaults to false when unset (#1240, #1271)server.relaymsg section for configuring the new draft/relaymsg capability; added the new relaymsg operator capability for exercising it (#1119)allow-environment-overrides config variable, allowing config options to be overridden by environment variables. See the manual for more details. (#1049, thanks @csmith!)server.ip-check-script for configuring IP check plugins (#68, #1267, thanks @moortens!)max-concurrency restriction to accounts.auth-script section. The recommended default value is 64 (0 or unset disable the restriction) (#1267)accounts.registration.allow-before-connect; this allows the use of the new REGISTER command before connecting to the server (#1075)hidden option in operator blocks: if set to true, operator status is hidden from commands like WHOIS that would otherwise display it (#1194)accounts.nick-reservation.forbid-anonymous-nick-changes, which forbids anonymous users from changing their nicknames after initially connecting (#1337, thanks @Amiga60077!)channels.invite-expiration, allowing invites to +i channels to expire after a given amount of time (#1171)/NICKSERV CLIENTS LOGOUT command for disconnecting clients connected to a user account (#1072, #1272, thanks @ajaspers!)INVITE for invite-only channels, including an UNINVITE command (#1171)REQUEST, APPROVE, and REJECT subcommands of HOSTSERV (#1346)PONG is now sent with the server name as the first parameter, matching the behavior of other ircds (#1249, thanks @jesopo!)+T no-CTCP user mode; this has been fixed (#1299, thanks @mogad0n!)/NICKSERV SAREGISTER of confusable nicknames (#1322, thanks @mogad0n!)LUSERS counts caused by KLINE (#1303, thanks @mogad0n!)CHATHISTORY queries for invalid channels now get an empty batch instead of a FAIL (#1322)fakelag.messages-per-window = 0 no longer causes a panic (#861, thanks @vertisan!)oragono importdb command for importing a converted Anope or Atheme database; see the manual for details (#1042)ip-check-script, a scripting API for restricting access by client IP. We provide oragono-dnsbl, an external script that can query DNSBLs for this purpose (#68, #1267, thanks @moortens!)+u. This is an "auditorium" mode that prevents unprivileged users from seeing each other's JOIN and PART lines. It's useful for large public-announcement channels, possibly in conjunction with +m (#1300)+U. This is an "op-moderated" mode; messages from unprivileged users are sent only to channel operators, who can then choose to grant them +v. (#1178)+b m:: users matching the ban expression (e.g., +b m:*!*@j6dwi4vacx47y.irc) will be able to join the channel, but will be unable to speak. (#307)379 RPL_WHOISMODES line to the WHOIS response, making it easier for operators to see other users' modes (#769, thanks @Amiga60077 and @KoraggKnightWolf!)/CHANSERV DEOP command for removing channel operator privileges (#361, thanks @RunBarryRun!)r flag to /WHO responses for registered nicknames (#1366, thanks @Amiga60077!)~u by default, instead of ~user; this can be changed by setting the coerce-ident field (#1340)/NICKSERV SUSPEND has been modified to take subcommands (ADD, DEL, and LIST); the ADD subcommand now accepts time duration and reason arguments. See /msg NickServ HELP SUSPEND for details. (#1274, thanks @mogad0n!)/NICKSERV SESSIONS is now /NICKSERV CLIENTS LIST, but the old command is still accepted (#1272, thanks @ajaspers!)SETNAME behavior for legacy clients (#1358, thanks @KoraggKnightWolf!)conventional.yaml to traditional.yaml (#1350)We're pleased to announce Oragono 2.3.0, a new stable release.
This release contains primarily bug fixes, but includes one notable feature enhancement: a change contributed by @hhirtz that updates the draft/rename specification to correspond to the new (soon-to-be) published draft.
Many thanks to @hhirtz for contributing patches, to @bogdomania, @digitalcircuit, @ivan-avalos, @jesopo, @kylef, @Mitaka8, @mogad0n, and @ProgVal for reporting issues and helping test, and to our translators for contributing translations.
This release includes no changes to the config file format or database changes.
lookup-hostnames for configurations that cloak IPs (as has been the default since 2.1.0) is now false (#1228)/HOSTSERV OFFERLIST and related commands; this functionality is superseded by IP cloaking (#1190)*playback not receiving echo-message when applicable (#1204, thanks @kylef!)draft/rename implementation to the latest draft (#1223, thanks @hhirtz!)/INFO now includes the Go version (#1234)Pre-release testing of 2.3.0-rc1 revealed serious bugs (#1251, #1252) that were introduced during the 2.3.0 development window. Accordingly, we're publishing a second release candidate for 2.3.0 that fixes these issues. We expect the official release of 2.3.0 next week; thanks for your patience.
Thanks to @mogad0n for help testing 2.3.0-rc1!
We're pleased to be publishing the release candidate for 2.3.0 (the official release should follow in a week or so).
This release contains primarily bug fixes, but includes one notable feature enhancement: a change contributed by @hhirtz that updates the draft/rename specification to correspond to the new (soon-to-be) published draft.
Many thanks to @hhirtz for contributing patches, to @bogdomania, @jesopo, @kylef, @Mitaka8,and @mogad0n for reporting issues and helping test, and to our translators for contributing translations.
This release includes no changes to the config file format or database changes.
lookup-hostnames for configurations that cloak IPs (as has been the default since 2.1.0) is now false (#1228)/HOSTSERV OFFERLIST and related commands; this functionality is superseded by IP cloaking (#1190)*playback not receiving echo-message when applicable (#1204, thanks @kylef!)draft/rename implementation to the latest draft (#1223, thanks @hhirtz!)/INFO now includes the Go version (#1234)We're pleased to announce Oragono 2.2.0, a new stable release.
This release contains several notable enhancements, as well as bug fixes:
Many thanks to @clukawski and @jesopo for contributing patches, to @ajaspers, @bogdomania, @csmith, @daurnimator, @emersonveenstra, @eskil, @eskimo, Geo-, @happyhater, @jesopo, @jwheare, @k4bek4be, @KoraggKnightWolf, @kylef, @LukeHoersten, @mogad0n, r3m, @RyanSquared, savoyard, and @wrmsr for reporting issues and helping test, and to our translators for contributing translations.
This release includes changes to the config file format, including one breaking change: timeout is no longer an acceptable value of accounts.nick-reservation.method. (If you were using it, we suggest strict as a replacement.) All other changes to the config file format are backwards compatible and do not require updating before restart.
This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Oragono. Otherwise, you can update the database manually by running oragono upgradedb (see the manual for complete instructions).
strict as the default enforcement method. Users who configured timeout for their account will be upgraded to strict. With accounts.login-via-pass-command enabled, clients lacking support for SASL can authenticate via the PASS (server password command) by sending account_name:account_password as the server password. (#1027)server.enforce-utf8, controlling whether the server enforces that messages be valid UTF-8; a value of true for this is now the recommended default (#1151)history.tagmsg-storage for configuring which TAGMSG are stored in history; if this is not configured, TAGMSG will not be stored (#1172)certfp instead of fingerprint (the old name of fingerprint is still accepted) (#1050, thanks @RyanSquared!)accounts.auth-script section for configuring external authentication scripts (#1107, thanks @daurnimator!)accounts.ldap section for configuring LDAP; LDAP is now available via the auth-script plugin interface (#1142)defcon operator capability, allowing use of the new /DEFCON command (#328)awaylen, kicklen, and topiclen limits now reflect the 512-character line limit (#1112, thanks @k4bek4be!)extjwt section for configuring the EXTJWT extension (#948, #1136)login-via-pass-command: true is now a recommended default (#1186)/NICKSERV SUSPEND and /NICKSERV UNSUSPEND commands, allowing operators to suspend access to an abusive user account (#1135)/DEFCON command, allowing operators to respond to spam or DoS attacks by disabling features at runtime without a rehash. (This feature requires that the operator have a newly defined capability, named defcon; this can be added to the appropriate oper blocks in the config file.) (#328, thanks @bogdomania!)BOT ISUPPORT token, plus a B flag for bots in 352 RPL_WHOREPLY (#1117)+T no-CTCP user mode (#1007, thanks @clukawski!)/NICKSERV REGISTER (#1179, thanks @LukeHoersten!)/NICKSERV SET PASSWORD now sends a warning (#1208)/LIST output (#1161, thanks @bogdomania!)INVITE not overriding a +b ban (#1168)CHGHOST lines during authentication with /NICKSERV IDENTIFY under some circumstances (#1108, thanks Geo-!)CHGHOST lines sent to users during connection registration (#1125, thanks @jesopo!)znc.in/playback capability, in particular restoring compatibility with Palaver (#1205, thanks @kylef!)/AWAY command (#1207)/NS SAREGISTER (#1216)\n (#1167, thanks @eskimo!)away-notify lines not being sent on channel JOIN (#1198, thanks savoyard!)/NICKSERV UNREGISTER and /NICKSERV ERASE not deleting stored user modes (#1157)/DLINE now operates on individual client connections (#1135)MONITOR list (#1053, thanks @ajaspers!)MONITOR L now lists the nicknames in the form they were originally sent with MONITOR +, without casefolding (#1083)445 ERR_SUMMONDISABLED and 446 ERR_USERSDISABLED in response to the SUMMON and USERS commands (#1078, thanks @KoraggKnightWolf!)= (#1067, #1069, #1091, thanks @KoraggKnightWolf and @jesopo!)history.tagmsg-storage config block (#1172)/NICKSERV CERT ADD with no argument now adds the user's current TLS certificate fingerprint, when applicable (#1059, thanks @emersonveenstra!)default.yaml, instead of oragono.yaml (#1130, thanks @k4bek4be!)/INFO command now includes the full git hash, when applicable (#1105)