IRC is the only backend without a retry loop. sockchat, Discord and Matrix each have run_with_retry with exponential backoff; IRC has none — run() returning ends the task and the account sits Disconnected until someone manually reconnects it.
Stated outright at backend/irc.rs:28-32: "No auto-reconnect in this milestone (see project plan) — a failure just reports connectionState 'disconnected' with an error and stops."
That was a reasonable milestone boundary; it is now the single most user-visible gap in the IRC backend, because a network blip on any other protocol is invisible and on IRC is permanent.
Done looks like: the same backoff shape the other three use (3s → 60s), with the existing MIN_RECONNECT_INTERVAL pacing and AuthFailed still terminal so a bad password does not spin forever.
Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho 1a11250, nobilis 030707f).
IRC is the only backend without a retry loop. sockchat, Discord and Matrix each have `run_with_retry` with exponential backoff; IRC has none — `run()` returning ends the task and the account sits `Disconnected` until someone manually reconnects it.
Stated outright at `backend/irc.rs:28-32`: "No auto-reconnect in this milestone (see project plan) — a failure just reports connectionState 'disconnected' with an error and stops."
That was a reasonable milestone boundary; it is now the single most user-visible gap in the IRC backend, because a network blip on any other protocol is invisible and on IRC is permanent.
**Done looks like:** the same backoff shape the other three use (3s → 60s), with the existing `MIN_RECONNECT_INTERVAL` pacing and `AuthFailed` still terminal so a bad password does not spin forever.
---
_Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho `1a11250`, nobilis `030707f`)._
Salastil
added the bug label 2026-08-29 09:59:41 -04:00
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.
IRC is the only backend without a retry loop. sockchat, Discord and Matrix each have
run_with_retrywith exponential backoff; IRC has none —run()returning ends the task and the account sitsDisconnecteduntil someone manually reconnects it.Stated outright at
backend/irc.rs:28-32: "No auto-reconnect in this milestone (see project plan) — a failure just reports connectionState 'disconnected' with an error and stops."That was a reasonable milestone boundary; it is now the single most user-visible gap in the IRC backend, because a network blip on any other protocol is invisible and on IRC is permanent.
Done looks like: the same backoff shape the other three use (3s → 60s), with the existing
MIN_RECONNECT_INTERVALpacing andAuthFailedstill terminal so a bad password does not spin forever.Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho
1a11250, nobilis030707f).Finished — nobilis
ce474ac