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

type: docker-compose
prepare:
  git: https://github.com/WeblateOrg/docker-compose.git
files:
  settings-override.py:
    content: |
      USE_X_FORWARDED_HOST = True
override:
  version: "3"
  services:
    weblate:
      ports:
        - "8080"
      environment:
        WEBLATE_DEBUG: 0
        WEBLATE_URL_PREFIX: !libervia_param [url_prefix, /weblate]
        WEBLATE_EMAIL_HOST: !libervia_conf ["", "email_server"]
        WEBLATE_EMAIL_HOST_USER: !libervia_conf ["", "email_username"]
        WEBLATE_EMAIL_HOST_PASSWORD: !libervia_conf ["", "email_password"]
        WEBLATE_SERVER_EMAIL: !libervia_conf ["", "email_from", "weblate@example.com"]
        WEBLATE_DEFAULT_FROM_EMAIL: !libervia_conf ["", "email_from", "weblate@example.com"]
        WEBLATE_SITE_DOMAIN: !libervia_conf ["", "public_url"]
        WEBLATE_ADMIN_PASSWORD: !libervia_generate_pwd
        WEBLATE_ADMIN_EMAIL: !libervia_conf ["", "email_admins_list", "", "first"]
        WEBLATE_ENABLE_HTTPS: !libervia_conf ["", "weblate_enable_https", "1"]
      volumes:
        - ./settings-override.py:/app/data/settings-override.py:ro
expose:
  url_prefix: [override, services, weblate, environment, WEBLATE_URL_PREFIX]
  front_url: !libervia_param [front_url, /translate]
  web_label: Translate
  ports:
    web:
      service: weblate
      private: 8080
  passwords:
    admin: [override, services, weblate, environment, WEBLATE_ADMIN_PASSWORD]