Merge pull request 'docs: the Discord bot login stays on @jared' (#49) from docs/discord-login-owner into main
Lint / Shell (shellcheck) (push) Successful in 15s
Lint / JS (eslint) (push) Successful in 12s
Lint / No secrets in webhook configs (push) Successful in 5s
Lint / Landing page is rendered (matrix (push) Successful in 5s
Lint / Python (ruff) (push) Successful in 5s
Lint / Python deps (pip-audit) (push) Successful in 1m53s
Lint / Secret scan (gitleaks) (push) Successful in 6s

This commit was merged in pull request #49.
This commit is contained in:
2026-10-28 22:19:19 -04:00
+5 -5
View File
@@ -427,11 +427,11 @@ can't overwrite the room's name and icon with the Discord channel's.
**Bot profile:** `@discordbot` shows as "Discord Bridge" with the Discord logo
(`discord-bridge/bot-avatar.png`). To reapply it: `pct exec 151 -- bash /opt/matrix-config/discord-bridge/set-bot-profile.sh`.
**Who the Discord bot login belongs to:** whichever Matrix account ran `login-token bot` sends its own
messages to Discord *as the bot* ("matrix-bridge APP"), not through the relay webhook. So it lives on a
dedicated account, `@discord-relay:matrix.lotusguild.org`, which never chats. Everyone else, admins
included, stays logged out of the bridge and is relayed under their own name and avatar. Logging the
bot in on one account automatically logs out any other account that had it.
**Who the Discord bot login belongs to:** `@jared` holds it. The account holding the login sends its
own messages to Discord *as the bot* ("matrix-bridge APP"), because the bridge prefers a real Discord
connection over the webhook. Everyone else is relayed through the channel webhook under their own name
and avatar. To change that, log the bot in from a dedicated non-chatting account; that automatically
logs out whichever account held it before.
**Rotating the bot token:** reset it in the Developer Portal, then DM the bridge bot `logout` and
`login-token bot <new token>`.