This was #414 and we already declared victory on this. But this still interests me as the best option for enterprise hardening of Oragono: with native support for this, we could immediately reject any connection that doesn't have a valid certificate. (In a hypothetical enterprise setting, rapidly expiring certificates would then be distributed by a management agent.)

it would be nice to be able to alter the 'static introduction' per chan from sedregex-plugin, since i want to conf different phrases/langs instead of 'meant to say' per #chan

$cargo run

Finished dev [unoptimized + debuginfo] target(s) in 0.13s
Running /home/folaht/testbot/devlohpmaq/target/debug/testbot
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })', src/main.rs:10:15
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

`$strace

Currently we have only one "accounts" and "oeprators" storage backend; "the config file" (ircd.yml).

In future we will have support for other configurable types of backends for "accounts"; meanwhile here is a proposal for improved accounts that integrate "operators" (currently split in the configuration file).

• A single "accounts" config block that holds account usernames and passwords

IRCv3 Specifications

IRCv3.1

Base Extensions

• Capability Negotiation
• multi-prefix Extension
• sasl Extension

Optional Extensions

• [account-notify Extension](http://ircv3.n