See 69448b13a1 / #1969; the compiler can now ensure that a uint64
intended for atomic access is always aligned to a 64-bit boundary.
Convert atomic operations on uint32s and pointers as well.

upgrade go to 1.19

fix #1980

Sanitize ::1 to 0::1 in WHOX output

upgrade dependencies for v2.11 release cycle

parallelize tests via the native go mechanism

Update Crowdin URL

fix #1969

On a 32-bit architecture, 64-bit atomic loads and stores must be aligned to a
64-bit boundary. Since the (mysql.MySQL) struct is directly included in the
Server struct, it is impossible to guarantee this via the standard technique
of putting the 64-bit value at the beginning of the struct definition
(since the point at which it is included in the parent struct may cross a
64-bit boundary).

This optimization is probably pointless anyway, adding an additional
indirection won't make a difference.

bump version and changelog for v2.10.0

only send MARKREAD to sessions with the read-marker cap

fix critical bugs in draft/read-marker

changelog updates for v2.10.0-rc1

fix #1905

* MANUAL.md: correct shebangs

* docs/{USERGUIDE,MANUAL}.md: mention amode +v joining through +i

* MANUAL.md: add a FAQ on special privileges of AMODEs

* USERGUIDE.md: add missing channel name

* MANUAL.md: mention that special privileges are cumulative

* Revert "MANUAL.md: correct shebangs"

This reverts commit 75a77c5537.

* MANUAL.md: restore syntax highlighting for python3

Co-authored-by: Aminda Suomalainen <suomalainen+git@mikaela.info>

Fixes #1697

NS SAREGISTER should send machine-readable responses. A simple approach:
check if the account-registration cap is enabled, and if so, send the
the same responses that would be sent by the REGISTER command.

exempt operators from history cutoffs

See #1593; this enables a client-side implementation of bulk deletion

Reported by @Mikaela

fix #1688

fix #1886

add SAVERIFY command

* Add ACCEPT-tracking functionality (authorizing users to send DMs
  despite +R or other applicable restrictions)
* Sending a DM automatically accepts the recipient
* Add explicit ACCEPT command

Add more clarify in NS INFO and SAREGISTER about unregistered nicknames

Fixes #1924

genericize atomic config changes