evoid-maubot

EVOID adapter for maubot — bridges Matrix events to Jitsi iframe commands via EVOID pipeline.

What It Does

Converts Matrix !jitsi commands into EVOID Intents, which map to Jitsi's 50+ iframe API commands. Full reference: https://jitsi.github.io/handbook/docs/dev-guide/dev-guide-iframe-commands/

Installation

# As EVOID plugin
evo plug install evoid-maubot

# As maubot plugin
cd packages/evoid-maubot
zip -9r evoid-maubot.mbp *
# Upload .mbp to maubot management interface

Commands

Room Management

Watch Party

Display

Media Control

Layout

Participants

Moderation

Chat

Recording

Breakout Rooms

Misc

Configuration

# base-config.yaml
service_name: maubot-bot
command_prefix: jitsi

jitsi:
  server_url: https://meet.example.com
  muc_domain: conference.meet.example.com
  admin_username: admin
  admin_password: secret

admin_whitelist:
  - "@admin:example.com"

storage:
  db_path: jitsi-bot.db
  enable_smart_routing: true

debug: false

Configuration Options

Storage

Optional persistence via evoid-sqlite and evoid-smart-storage:

pip install evoid-maubot[storage]

Data stored:

Storage is optional — bot works without it but won't persist data across restarts.

EVOID Integration

Each command maps to a Jitsi iframe API command. The flow:

!jitsi watch https://youtube.com/watch?v=abc
    ↓
Matrix Event → Adapter → Intent(name="jitsi:watch", level=STANDARD)
    ↓
Pipeline: validate → authorize
    ↓
Handler returns: {iframe_command: "startShareVideo", args: {url: "..."}}
    ↓
Jitsi executes command in user's browser

Moderator commands use level=CRITICAL for full pipeline (validate → authorize → audit → protect).

The plugin uses evoid.native.on to register intents with the EVOID message bus. Intents are published via evoid.publish and routed through the IOP pipeline.

Development

uv venv && uv pip install -e ".[dev]"
ruff check evoid_maubot/
ruff format evoid_maubot/
pytest tests/ -v

License

Apache-2.0