« Changelog History


Oragono v0.11.0 Release Notes

Release Date: 2018-04-15 // about 6 years ago

  • 🚀 And v0.11.0 finally comes along! This release has been in the works for almost four months now, with an alpha and beta helping square away the issues.

    📚 We're adding a lot of features to improve debugging, better support international users, and make things better for network administrators. Among the new features, you can use the LANGUAGE command to set a custom server language (see our CrowdIn to contribute), expose a debugging pprof endpoint, reserve nicknames with NickServ, and force email verification for new user accounts. On the improvements side we have a CAP REQ fix, and we now have a manual that contains a nice overview of Oragono's documentation.

    🚀 If you have any trouble with this release, please let us know with an issue on our tracker, or by talking to us in #oragono on Freenode.

    🚀 Thanks a bunch to everyone for the help with this release – especially to our translators and to Slingamn for being an awesome co-maintainer!

    Config Changes

    • 🔧 callbacks section added under accounts/registration, configuring our new email verification (disabled by default).
    • 🔧 fakelag section added, configuring our new fakelag implementation.
    • ips-per-subnet key renamed to connections-per-subnet.
    • 0️⃣ motd-formatting is now enabled by default.
    • 🔧 nick-reservation section added under accounts, configuring our new nickname ownership abilities.
    • nofakelag and unregister oper classes added.
    • 0️⃣ pprof-listener key added under debug (disabled by default).
    • 👍 skip-server-password key added under accounts, to better support certain clients.
    • 0️⃣ verify-timeout default value changed from 120 hours to 32 hours under accounts/registration.

    ➕ Added

    • ➕ Added 32-bit builds.
    • ➕ Added a debug pprof endpoint, which is disabled by default and can be exposed in the config.
    • ➕ Added a manual to our documentation! This is primarily where we'll be adding user-facing information and instructions from now on.
    • ➕ Added current running git commit to the sent version string.
    • ➕ Added fakelag, so that the server can slow down clients hitting it too aggressively. Disabled by default while we work out the kinks and the specific settings (thanks @slingamn!).
    • ➕ Added IRCv3 capability batch and draft capability draft/labeled-response.
    • ➕ Added listening support for unix sockets.
    • ➕ Added new Brazilian Portuguese translation (thanks to Alexandre Oliveira!)).
    • ➕ Added new French translation (thanks to Joshua!).
    • ➕ Added new Norwegian translation (thanks to Morten!).
    • ➕ Added new subcommands to CHANSERV, including:
      • OP to op yourself or the given user (can only be run by channel founders).
    • ➕ Added new subcommands to NICKSERV, including:
      • DROP to de-associate a nickname from your current account.
      • GHOST to remove the given client (if they're logged in with your user account).
      • GROUP to associate a nickname with your current account.
      • IDENTIFY to login to an account.
      • INFO to see information about the given (or your own) account.
      • REGISTER to register an account.
      • UNREGISTER to delete your account.
    • ➕ Added new Turkish translation (thanks to Yaser!).
    • ➕ Added proposed IRCv3 capabilities draft/languages and draft/resume.
    • ➕ Added the ability to associate multiple nicknames with your account, and enforce nickname ownership.
    • ➕ Added the ability to force email verification when users register accounts.
    • ➕ Added user modes, including:
      • B: Mark yourself as a bot, and display that you're a bot in WHOIS.

    🔄 Changed

    • genpasswd now requires that you confirm the input passphrase.
    • Message IDs are now much shorter and easier to read – down from 39 characters to 16 while preserving a very similar gaurantee of uniqueness (thanks @prawnsalad for bringing up this issue).

    🛠 Fixed

    • We now correctly suspend registration when receiving a CAP REQ, as per the spec.
    • We now properly cut off clients who try to send us too much data at once.