listProtocols (rpc/methods.rs:79-90) returns Slack, and SettingsPanel.tsx carries a Slack category — but there is no addSlackAccount arm anywhere in the dispatcher, so calling it falls through to unknown method.
XMPP at least answers honestly: addXmppAccount returns "not implemented yet". Slack does not even do that.
This is the UI advertising something that does not exist, which is worse than not listing it.
Done looks like: either drop Slack (and XMPP) from listProtocols and the Settings rail until a backend exists, or add an addSlackAccount arm that returns the same honest "not implemented yet". The first is preferable — a protocol list should describe what can be connected. Tracked separately as the real work in #24.
Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho 1a11250, nobilis 030707f).
`listProtocols` (`rpc/methods.rs:79-90`) returns Slack, and `SettingsPanel.tsx` carries a Slack category — but there is no `addSlackAccount` arm anywhere in the dispatcher, so calling it falls through to `unknown method`.
XMPP at least answers honestly: `addXmppAccount` returns "not implemented yet". Slack does not even do that.
This is the UI advertising something that does not exist, which is worse than not listing it.
**Done looks like:** either drop Slack (and XMPP) from `listProtocols` and the Settings rail until a backend exists, or add an `addSlackAccount` arm that returns the same honest "not implemented yet". The first is preferable — a protocol list should describe what can be connected. Tracked separately as the real work in #24.
---
_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:42 -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.
listProtocols(rpc/methods.rs:79-90) returns Slack, andSettingsPanel.tsxcarries a Slack category — but there is noaddSlackAccountarm anywhere in the dispatcher, so calling it falls through tounknown method.XMPP at least answers honestly:
addXmppAccountreturns "not implemented yet". Slack does not even do that.This is the UI advertising something that does not exist, which is worse than not listing it.
Done looks like: either drop Slack (and XMPP) from
listProtocolsand the Settings rail until a backend exists, or add anaddSlackAccountarm that returns the same honest "not implemented yet". The first is preferable — a protocol list should describe what can be connected. Tracked separately as the real work in #24.Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho
1a11250, nobilis030707f).Finished — nobilis
4c3c13f