LotusGuild/matrix
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: voice bridge live — bot profile, room setup, upgrade steps #52

Merged
jared merged 1 commits from docs/voice-bridge-live into main 2026-10-29 13:24:36 -04:00
Conversation 0 Commits 1 Files Changed 1
+8 -3
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8 -3
View File
@@ -460,11 +460,14 @@ as `[Matrix] <name>`, with mute mirrored to Discord.
| Matrix (Lotus) | Discord Bridge (mautrix-discord) | Discord Voice Bridge (`!yS_ZIHL3sOKQJBt4NiIQyiHKt3cv6HrIDeq7OxDpSM0`) | | Matrix (Lotus) | Discord Bridge (mautrix-discord) | Discord Voice Bridge (`!yS_ZIHL3sOKQJBt4NiIQyiHKt3cv6HrIDeq7OxDpSM0`) |
- **Build:** upstream [nether-voicebridge](https://nether.codes/nether/nether-voicebridge) `cf52945` - **Build:** upstream [nether-voicebridge](https://nether.codes/nether/nether-voicebridge) `cf52945`
plus 11 Lotus patches (reported upstream). Patches, bug log and issue drafts live in plus 12 patches to report upstream and 1 Lotus-only patch: Discord users without an avatar get
Discord's default one. Patches, bug log and issue drafts live in
`/root/code/voice-bridge-trial/`. **Don't run the unpatched release**. Without the patches the `/root/code/voice-bridge-trial/`. **Don't run the unpatched release**. Without the patches the
bridge can't see anyone using current Element Call or Lotus Call (`livekit_alias`), and encrypted bridge can't see anyone using current Element Call or Lotus Call (`livekit_alias`), and encrypted
voice breaks after a restart on Synapse. voice breaks after a restart on Synapse.
- **Accounts:** the bot is `@lotus-voice_bot`, shown in encrypted calls as "Discord Voice Bridge". - **Accounts:** the bot is `@lotus-voice_bot`, shown as "Discord Voice Bridge" with the Discord logo.
It has **no special power** in the room; it only needs calls at power level 0. The room has the
Discord logo, a topic, and an `m.bridge` record, so Lotus shows the Discord chip linking to the channel.
Discord speakers are `@lotus-voice_<discord id>`. The appservice registration is Discord speakers are `@lotus-voice_<discord id>`. The appservice registration is
`/etc/matrix-synapse/lotus-voice-registration.yaml`. `/etc/matrix-synapse/lotus-voice-registration.yaml`.
- **Discord bots:** Lotus Voice 1–3, one per Matrix person speaking at once. Each has only Connect, - **Discord bots:** Lotus Voice 1–3, one per Matrix person speaking at once. Each has only Connect,
@@ -480,7 +483,9 @@ as `[Matrix] <name>`, with mute mirrored to Discord.
- **Install / upgrade:** on the Proxmox node hosting LXC 151, run - **Install / upgrade:** on the Proxmox node hosting LXC 151, run
`bash voice-bridge/install.sh <binary> <secrets file with BOT1..BOT3>`. The first install `bash voice-bridge/install.sh <binary> <secrets file with BOT1..BOT3>`. The first install
registers the appservice, restarts Synapse once and creates the bot account. Then invite registers the appservice, restarts Synapse once and creates the bot account. Then invite
`@lotus-voice_bot:matrix.lotusguild.org` to the voice room. Upgrades just swap the binary. `@lotus-voice_bot:matrix.lotusguild.org` to the voice room. **To upgrade:** push the new binary to
`/opt/lotus-voice/lotus-voice-bridge` (keep the old one as `.prev`), then run
`systemctl restart lotus-voice-bridge`. Synapse isn't touched.
## Bot profiles ## Bot profiles