plugin XEP-0353, XEP-0234, jingle: WebRTC data channel signaling implementation: Implement XEP-0343: Signaling WebRTC Data Channels in Jingle. The current version of the XEP (0.3.1) has no implementation and contains some flaws. After discussing this on xsf@, Daniel (from Conversations) mentioned that they had a sprint with Larma (from Dino) to work on another version and provided me with this link: https://gist.github.com/iNPUTmice/6c56f3e948cca517c5fb129016d99e74 . I have used it for my implementation. This implementation reuses work done on Jingle A/V call (notably XEP-0176 and XEP-0167 plugins), with adaptations. When used, XEP-0234 will not handle the file itself as it normally does. This is because WebRTC has several implementations (browser for web interface, GStreamer for others), and file/data must be handled directly by the frontend. This is particularly important for web frontends, as the file is not sent from the backend but from the end-user's browser device. Among the changes, there are: - XEP-0343 implementation. - `file_send` bridge method now use serialised dict as output. - New `BaseTransportHandler.is_usable` method which get content data and returns a boolean (default to `True`) to tell if this transport can actually be used in this context (when we are initiator). Used in webRTC case to see if call data are available. - Support of `application` media type, and everything necessary to handle data channels. - Better confirmation message, with file name, size and description when available. - When file is accepted in preflight, it is specified in following `action_new` signal for actual file transfer. This way, frontend can avoid the display or 2 confirmation messages. - XEP-0166: when not specified, default `content` name is now its index number instead of a UUID. This follows the behaviour of browsers. - XEP-0353: better handling of events such as call taken by another device. - various other updates. rel 441

#!/bin/bash

SETUP_INDICATOR="/home/libervia/.local/share/libervia/setup_complete.flag"
FORUMS_JSON_FILE="/home/libervia/forums.json"

if [ ! -f "$SETUP_INDICATOR" ]; then
    echo "First run detected. Setting up the environment and configuration."

    # we create the file sharing component which will autoconnect when backend is started
    libervia-cli profile create file-sharing -j files.server1.test -p "" --xmpp-password test_e2e -C file-sharing -A
    # we have to be sure that file-sharing is connected before demo account,
    # otherwise disco will be cached without it, and feature such as file
    # sharing won't be available.
    libervia-cli profile connect -cp file-sharing
    # create a demo account
    libervia-cli profile create demo -j demo@server1.test -p "demo"
    libervia-cli profile modify -D -cp demo --pwd demo
    libervia-cli forums set -p demo < $FORUMS_JSON_FILE
    libervia-cli bookmarks add -pdemo -a demo@chat.server1.test

    touch "$SETUP_INDICATOR"
    echo "Initial setup complete."
else
    echo "Not the first run. Skipping setup."
fi