Jitsi Meet

When developing or extending Prosody modules for Jitsi, follow these data storage patterns to ensure stability and prevent memory leaks:

1. Storage Location: Store data within the room._data object or directly on the room object.
2. Data Types: Data must be simple types, such as strings or a table of strings.
3. Avoid Complex Objects: Do not attach complex objects like room, sessions, or occupants to the data, as these cannot be serialized.
4. Lifecycle Safety: Attaching data to the room object ensures that data is automatically wiped when the room is destroyed and makes module reloading safe.

The persistence layer uses JSON.stringify() for serialization. Consequently, you cannot persist complex JavaScript objects that are not JSON-compatible.

Unsupported types include:

• Map
• Set
• Function

Ensure that any state you intend to persist via PersistenceRegistry consists only of JSON-serializable data.

The Waiting Queue service distinguishes between Visitors and Moderators based on the claims within their JWT context.

Visitor Token Requirements

To allow a user to connect to the /visitor websocket and wait for the 'ready to join' message, the token must contain:

{
  "context": {
    "user": {
      "role": "visitor"
    }
  }
}

Moderator Token Requirements

To allow a moderator to connect to the /moderator websocket and receive visitor count updates via the /secured/conference/state/topic.{conference} topic, the token must contain:

{
  "context": {
    "user": {
      "moderator": true
    }
  }
}

To connect to the Waiting Queue service, you must provide a JWT token in the Authorization header of the STOMP CONNECT message. The token must be a valid JAAS token for the specific conference.

When subscribing to topics, ensure the Authorization header is also included in the subscription request.

headers = {
    Authorization: 'Bearer ' + token
};

stompClient.connectHeaders = headers;

stompClient.onConnect = (frame) => {
    setConnected(true);
    console.log('Connected: ' + frame);

    stompClient.subscribe('/secured/conference/visitor/topic.' + conference, (message) => {
        showMessage(message.body);
    }, headers);
};

To use fastlane for automation in this project, ensure you have the latest version of the Xcode command line tools installed first. You can then install fastlane using either RubyGems or Homebrew.

xcode-select --install

# Using RubyGems
[sudo] gem install fastlane -NV

# OR using Homebrew
brew install fastlane

Jitsi Meet is a browser-based video conferencing platform. You can use it immediately without installation by visiting meet.jit.si. To start a meeting, you may need a Google, Facebook, or GitHub account.

For mobile users, Jitsi Meet is available via mobile web browsers or through dedicated native applications:

• Android: Available on Google Play and F-Droid.
• iOS: Available on the App Store.

Early access to new features can be obtained through the open beta programs for Android and iOS (via TestFlight).

Jitsi Meet uses the i18next library for translations, with each language stored in a separate JSON file. To translate Jitsi Meet, you must manually edit these language files.

To simplify the process, you can use the update-translation.js script to identify missing keys. Running this script against a specific language file will update it with all missing keys set to empty strings, allowing you to simply fill in the translations.

cd lang
node update-translation.js main-es.json

To support camera, microphone, and background audio, perform the following steps on iOS:

1. Info.plist: Add Privacy - Camera Usage Description and Privacy - Microphone Usage Description.
2. Signing & Capabilities: Enable the following Background modes:
   • Audio
   • Voice over IP
   • Background fetch
3. Install Pods: Run pod install from the ios directory.

cd ios && pod install && cd ..