The only capability ever requested is sasl (backend/irc.rs:352), followed immediately by CAP END.
Most consequential is server-time: without it every message is stamped with the local clock at receive (runtime.rs:1448), so anything replayed or backfilled dates itself to now rather than when it was said.
Also absent: chathistory (the only real path to IRC backfill), echo-message, away-notify and account-notify (other users' away state is never known), multi-prefix, extended-join, message-tags, batch, labeled-response, setname, chghost.
Related: ISUPPORT is rendered as a server-buffer line and then discarded, so PREFIX, CHANMODES and CASEMAPPING are unparsed and rank prefixes are hardcoded ~ @ % + — wrong on any network that differs.
Done looks like:server-time and multi-prefix first (small, and they fix visibly wrong data), then away-notify/account-notify, then chathistory as its own piece of work.
Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho 1a11250, nobilis 030707f).
The only capability ever requested is `sasl` (`backend/irc.rs:352`), followed immediately by `CAP END`.
Most consequential is **`server-time`**: without it every message is stamped with the local clock at receive (`runtime.rs:1448`), so anything replayed or backfilled dates itself to now rather than when it was said.
Also absent: `chathistory` (the only real path to IRC backfill), `echo-message`, `away-notify` and `account-notify` (other users' away state is never known), `multi-prefix`, `extended-join`, `message-tags`, `batch`, `labeled-response`, `setname`, `chghost`.
Related: `ISUPPORT` is rendered as a server-buffer line and then discarded, so `PREFIX`, `CHANMODES` and `CASEMAPPING` are unparsed and rank prefixes are hardcoded `~ @ % +` — wrong on any network that differs.
**Done looks like:** `server-time` and `multi-prefix` first (small, and they fix visibly wrong data), then `away-notify`/`account-notify`, then `chathistory` as its own piece of work.
---
_Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho `1a11250`, nobilis `030707f`)._
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The only capability ever requested is
sasl(backend/irc.rs:352), followed immediately byCAP END.Most consequential is
server-time: without it every message is stamped with the local clock at receive (runtime.rs:1448), so anything replayed or backfilled dates itself to now rather than when it was said.Also absent:
chathistory(the only real path to IRC backfill),echo-message,away-notifyandaccount-notify(other users' away state is never known),multi-prefix,extended-join,message-tags,batch,labeled-response,setname,chghost.Related:
ISUPPORTis rendered as a server-buffer line and then discarded, soPREFIX,CHANMODESandCASEMAPPINGare unparsed and rank prefixes are hardcoded~ @ % +— wrong on any network that differs.Done looks like:
server-timeandmulti-prefixfirst (small, and they fix visibly wrong data), thenaway-notify/account-notify, thenchathistoryas its own piece of work.Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho
1a11250, nobilis030707f).Finished — nobilis
52af1b4