1.3 KiB
1.3 KiB
Intent: Matrix-Native MusicLink Routing
The Volition (Why)
- Surface Request: Make MusicLink a native Matrix bot that listens to multiple rooms and replies in the same originating room/thread, removing Matterbridge from routing.
- Deep Volition: Eliminate cross-room fan-out and accidental cross-posting (including DM leakage) while keeping MusicLink simple to run and correct in multi-room deployments.
- The "Done" State: MusicLink safely monitors multiple Matrix rooms, replies only where the message originated (and in-thread when applicable), and no longer relies on Matterbridge for routing.
The Context
- Constraints:
- Maintain existing MusicLink link parsing and response behavior.
- Keep mautrix-slack in place for Slack ↔ Matrix bridging.
- Prefer minimal operational complexity (single service/config/token).
- Silent Requirements:
- Avoid cross-posting across rooms.
- Preserve correct reply threading semantics.
- Ignore bot self-messages to prevent loops.
- Keep configuration explicit about which rooms are monitored.
The Anti-Goals
- Replacing mautrix-slack or altering Slack ↔ Matrix bridging.
- Adding new link providers or changing MusicLink’s core feature set.
- Relying on multi-gateway Matterbridge setups for routing correctness.