Release v1.1.3 · amiantos/lurker

What's Changed

Fixed an issue where the big migration in the last release could take a long time and cause problems with external database replication...
Fixed an issue where push devices for native apps were mislabeled in the web client's notification client list
Added client protocol spec / guide to the docs site
If a server provides a timestamp for a message, we record that timestamp and not the time we received the message.
We're also internally recording msgid to lay the groundwork for possible future reply / react support.
The server now reports accurate notify status on message arrivals that properly reflect the ignore rules.
Fixed an issue where the /part command didn't work as expected.
Overhauled the "automatically reconnect" system so it will actually, like, reconnect you reliably, automatically.
Fixed an issue (hopefully) that caused the message list and/or input bar to disappear on mobile Chrome.
Admin screens like invites and users will automatically refresh as you click on them, so stale data doesn't persist confusingly.
mIRC color codes are properly stripped from notifications.

Run the v16 buffers cutover as BEGIN IMMEDIATE by @amiantos in #603
Label native push devices by transport instead of user agent by @amiantos in #604
docs: Client Protocol & API spec for third-party client authors by @amiantos in #609
docs: surface Developers as a top-nav dropdown by @amiantos in #610
Store IRCv3 server-time + msgid; adopt echo-message for own sends by @amiantos in #611
Fold the ignore/mute veto into the server notify flag by @amiantos in #614
/part: leave the current channel with a reason by @amiantos in #615
Own the IRC reconnect policy: retry-forever with backoff by @amiantos in #618
Fix blank message lists (hydration reconciler) and the vanishing mobile-Chrome input bar by @amiantos in #619
Admin screens auto-refresh + strip mIRC codes from notifications by @amiantos in #620
Bump version to 1.1.3 by @amiantos in #621

Full Changelog: v1.1.2...v1.1.3