I think that 'moderator vs admin' is a pretty common set of priv levels,
whereas 'oper vs admin' is a little confusing, esp. to less irc-savvy
people.

/SAJOIN and /SAMODE are really common for joining channels to check out
what's going on and for e.g. opping someone when nobody in the channel
is opered, so it makes sense for mods to have those. I feel similarly
about vhosts, they're usually something that's delegated to less-prived
opers.

Changed the whois line from 'a server admin' to 'the server admin' to
make it a bit more clear that this is one single user, rather than a set
of privs to be shared. And it's a tiny thing, but removed the 'less
privileged' term from alice's oper block because it felt a bit dodgy.

See #1426

fix #1421

Allow custom limit definitions that encompass multiple subnets

fix #1345

validate amode recipients during data import

enhancements to database import

atheme2json enhancements

Convert the flat list of channels for always-on clients
to a map from channel names to channel-user modes.

Store the channel-user modes of always-on clients along with their
channel memberships, restore them on server startup. This will coexist
alongside /CS AMODE, which autoapplies modes to clients on join regardless
of their always-on status.

fix #1417

Allow `JOIN 0` with a confirmation code

fix TAGMSG being relayed to clients without message-tags

more memory-efficient implementation of line reading

fix #1409

fix #1396

add network name to RPL_WELCOME

Record INVITE in DM history for the benefit of offline always-on clients

* Defer account login snomask until after connection registration is complete
* Don't send account-notify for pre-registration clients

fix #1411

Clients without event-playback should receive client-only tags in
replayed PRIVMSG / NOTICE.

fix #1387

fix #1407

Fixes #1407

New Crowdin updates

Make atheme2json sort channel modes

This makes invoking the script multiple times with the same input return
the same result, which may not be the case before because sets are
unordered and thus the channel modes can become reordered across
multiple invocations of the script.

Allow atheme2json to handle mlock mode removal (outside of `-t` or `-n`)

For example, if the mlock is set to `-i`, `i` is not present in the
`modes` and thus it would error.

I'm inclined to think that the negative mlock feature doesn't behave
correctly, because the mlock of `-i` (or `-n`) would prevent anyone from
ever setting those modes on the channel. Which this does not appear to
be the case.

Fixes #1401

Instead of building a new serialized message for each recipient,
try to cache them.

mention UN[DK]LINE in [DK]LINE help

fix duplicated JOIN line sent to some resuming clients

Resuming clients without the resume capability would receive
two JOIN lines per channel.

docs/MANUAL.md: fix atheme2json link