module

Modular A/V: Jitsi

Endorsements
0
Installs
0.00%
Comments
0
Latest version0.15.0
Minimum Core14
Compatible Core14.369
Last updated3 hours ago
Created3 hours ago
Authors
Languages English
Systems All systems
Project source Project URL
Report bugs Bug tracker URL
License License URL

A service for Modular A/V that carries calls over your own Jitsi Meet server, with token authentication.

Requires Modular A/V (modular-av) and a self-hosted Jitsi Meet server.

meet.jit.si and 8x8's Jitsi as a Service aren't supported.

The module's settings: the server's address and domains, and the app id and secret kept in this browser only

Setting it up

  1. Run a self-hosted Jitsi Meet server (tested with docker-jitsi-meet stable-11248-2) with:
    • token (JWT) authentication, and no guests;
    • Prosody's presence_identity module on the main VirtualHost. It isn't on in any of Jitsi's default setups, and it is what stops a modified client from claiming to be another player;
    • no moderator rights for players: a Jitsi server with tokens makes everyone a moderator by default, and a moderator's client can mute or remove others;
    • its XMPP WebSocket reachable from players' browsers.
    The documentation lists the exact docker-jitsi-meet settings for each.
  2. In the module's settings, as a GM: the Jitsi server address (world), its XMPP and conference domains if they don't follow the address, and the Jitsi app id and secret (this browser only). Enter them in each browser a GM uses to run the game.
  3. If the world has more than one service enabled, choose Jitsi in Modular A/V's settings, under Voice and video service.

How players join

  • The secret never leaves the GM's browser.
  • A player's browser asks a GM's for a token. The GM's browser signs a short-lived one for that player alone and this world's room, with no moderator rights.
  • So a GM must be online for players to join or reconnect. Until then, players are told they're waiting for a GM. When a token runs out during a long call, the player's browser gets a fresh one without leaving the call.

What's different from LiveKit

  • Jitsi's tokens can't limit what a player sends, so a GM's block is enforced by everyone else's browser, which refuses that player's audio or video and asks the server not to send it.
  • Every call goes through the server, even for two players.
  • A shared screen carries its picture only, not its sound: Jitsi sends one sound track per player.
  • End-to-end encryption, the lobby, recording and transcription aren't supported.
  • Servers much older or newer than the tested one may not work: Jitsi publishes no rule for which versions of its client and server work together.

Good to know

  • Requires Foundry v14 and Modular A/V. Tested in Chromium browsers.
  • Network: only the Jitsi server the GM entered. lib-jitsi-meet's analytics, statistics and log collection stay off.
  • Jitsi's client puts the token in the WebSocket's address, so it can show in the browser's console and in your server's logs while it is valid (ten minutes). Don't log query strings on the server or its proxy.
  • Storage: the server's address and domains in world settings, and the app id and secret in the GM's browser only.
  • License: MIT. It ships lib-jitsi-meet v2205.0.0 (Apache-2.0) unmodified: Jitsi's own build, downloaded from Jitsi's GitHub release when the module is built and checked against a pinned SHA-256 hash. The notices are in the module's THIRD-PARTY-NOTICES.md.

Links

Subscribe
Notify of
0 Comments
0
Would love your thoughts, please comment.x
()
x