addDiscordAccountPassword (nobilis/src/rpc/methods.rs:2667) signs in with a username
and password, handles the two-factor challenge, and reports the result. Nothing in the
window calls it.
The account dialog offers exactly two ways in - 'qr' | 'browser'
(src/renderer/src/components/AccountsPanel.tsx:873).
What makes this worth fixing rather than deleting is that the flow is already half
wired: the two-factor step addDiscordAccountPassword kicks off arrives as a discordLoginMfa event and is answered with submitDiscordMfa, and submitDiscordMfa
is called from the window already. The back half of the flow is built and reachable.
Only the front half has no way in.
Found by a September 2026 sweep of all 182 daemon RPC methods against every string
literal in src/. setKickChatMode was excluded on purpose: it is unreachable too, and
says so in its own comment (#167). The methods listed as superseded by that sweep - uploadFile, listDiscordCommands, setMatrixIgnored, openIrcQuery, setMatrixRoomState, unsubscribe - are fine and want nothing.
`addDiscordAccountPassword` (`nobilis/src/rpc/methods.rs:2667`) signs in with a username
and password, handles the two-factor challenge, and reports the result. Nothing in the
window calls it.
The account dialog offers exactly two ways in - `'qr' | 'browser'`
(`src/renderer/src/components/AccountsPanel.tsx:873`).
What makes this worth fixing rather than deleting is that the flow is already half
wired: the two-factor step `addDiscordAccountPassword` kicks off arrives as a
`discordLoginMfa` event and is answered with `submitDiscordMfa`, and **`submitDiscordMfa`
is called from the window already**. The back half of the flow is built and reachable.
Only the front half has no way in.
---
Found by a September 2026 sweep of all 182 daemon RPC methods against every string
literal in `src/`. `setKickChatMode` was excluded on purpose: it is unreachable too, and
says so in its own comment (#167). The methods listed as superseded by that sweep -
`uploadFile`, `listDiscordCommands`, `setMatrixIgnored`, `openIrcQuery`,
`setMatrixRoomState`, `unsubscribe` - are fine and want nothing.
Finished - retired rather than wired up. The password form was removed on purpose in 1acde64 (Discord refuses a password from a third-party client and counts each attempt against the account); the browser route, now labelled Password, is where a password goes.
https://git.salastil.com/Salastil/nobilis/commit/c3c399d
https://git.salastil.com/Salastil/moho/commit/035fb73
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.
addDiscordAccountPassword(nobilis/src/rpc/methods.rs:2667) signs in with a usernameand password, handles the two-factor challenge, and reports the result. Nothing in the
window calls it.
The account dialog offers exactly two ways in -
'qr' | 'browser'(
src/renderer/src/components/AccountsPanel.tsx:873).What makes this worth fixing rather than deleting is that the flow is already half
wired: the two-factor step
addDiscordAccountPasswordkicks off arrives as adiscordLoginMfaevent and is answered withsubmitDiscordMfa, andsubmitDiscordMfais called from the window already. The back half of the flow is built and reachable.
Only the front half has no way in.
Found by a September 2026 sweep of all 182 daemon RPC methods against every string
literal in
src/.setKickChatModewas excluded on purpose: it is unreachable too, andsays so in its own comment (#167). The methods listed as superseded by that sweep -
uploadFile,listDiscordCommands,setMatrixIgnored,openIrcQuery,setMatrixRoomState,unsubscribe- are fine and want nothing.Finished - retired rather than wired up. The password form was removed on purpose in
1acde64(Discord refuses a password from a third-party client and counts each attempt against the account); the browser route, now labelled Password, is where a password goes.https://git.salastil.com/Salastil/nobilis/commit/c3c399d
https://git.salastil.com/Salastil/moho/commit/035fb73