From 993fd04353cc0a54fe1276a3bbc7b381a7ea1334 Mon Sep 17 00:00:00 2001 From: Valere Date: Thu, 13 Aug 2020 19:09:36 +0200 Subject: [PATCH 1/2] Update jitsi.md Updated Element Android section --- docs/jitsi.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/docs/jitsi.md b/docs/jitsi.md index 2ae8d9a785..76b49c9c73 100644 --- a/docs/jitsi.md +++ b/docs/jitsi.md @@ -50,7 +50,22 @@ default, and you are using riot-web 1.6 or newer, set the following on your home } ``` -## Mobile app support +## Element Android + +Element Android (1.0.5+) supports custom jitsi domain. + +1:1 calls, or calls between you and one other person, do not use Jitsi. Instead, those +calls work directly between clients or via TURN servers configured on the respective +homeservers. + +For rooms with more than 2 joined members, when creating a jitsi conference via call/video buttons of the toolbar (not via integration manager), Element Android will create a widget using app.element.io [wrapper](https://github.com/vector-im/element-web/blob/develop/docs/jitsi-dev.md) as url. +The domain used is the one specified by the `/.well-known/matrix/client` endpoint, and if not present it uses the fallback defined in `confix.xml` (jitsi.riot.im) + +For active jitsi widgets in the room, a native jitsi widget UI is created and points to the instance specified in the `domain` key of the widget content data. + +Element android manages allowed native widgets permissions a bit differently than web widgets (as the data shared are different, and never shared with the widget url). For jitsi widgets permissions is asked only once per domain (consent saved in account data). + +## Element IOS Currently the Element mobile apps do not support custom Jitsi servers and will instead use the default `jitsi.riot.im` server. When users on the mobile apps join the call, From 8cfb0a71a0df6fe071131f6db33ff1099e0b0a39 Mon Sep 17 00:00:00 2001 From: "J. Ryan Stinnett" Date: Wed, 19 Aug 2020 18:18:50 +0100 Subject: [PATCH 2/2] Apply suggestions from code review --- docs/jitsi.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/jitsi.md b/docs/jitsi.md index 76b49c9c73..d289cc3818 100644 --- a/docs/jitsi.md +++ b/docs/jitsi.md @@ -52,20 +52,20 @@ default, and you are using riot-web 1.6 or newer, set the following on your home ## Element Android -Element Android (1.0.5+) supports custom jitsi domain. +Element Android (1.0.5+) supports custom Jitsi domains, similar to Element Web above. 1:1 calls, or calls between you and one other person, do not use Jitsi. Instead, those calls work directly between clients or via TURN servers configured on the respective homeservers. -For rooms with more than 2 joined members, when creating a jitsi conference via call/video buttons of the toolbar (not via integration manager), Element Android will create a widget using app.element.io [wrapper](https://github.com/vector-im/element-web/blob/develop/docs/jitsi-dev.md) as url. -The domain used is the one specified by the `/.well-known/matrix/client` endpoint, and if not present it uses the fallback defined in `confix.xml` (jitsi.riot.im) +For rooms with more than 2 joined members, when creating a Jitsi conference via call/video buttons of the toolbar (not via integration manager), Element Android will create a widget using the [wrapper](https://github.com/vector-im/element-web/blob/develop/docs/jitsi-dev.md) hosted on `app.element.io`. +The domain used is the one specified by the `/.well-known/matrix/client` endpoint, and if not present it uses the fallback defined in `config.xml` (jitsi.riot.im) -For active jitsi widgets in the room, a native jitsi widget UI is created and points to the instance specified in the `domain` key of the widget content data. +For active Jitsi widgets in the room, a native Jitsi widget UI is created and points to the instance specified in the `domain` key of the widget content data. -Element android manages allowed native widgets permissions a bit differently than web widgets (as the data shared are different, and never shared with the widget url). For jitsi widgets permissions is asked only once per domain (consent saved in account data). +Element Android manages allowed native widgets permissions a bit differently than web widgets (as the data shared are different and never shared with the widget URL). For Jitsi widgets, permissions are requested only once per domain (consent saved in account data). -## Element IOS +## Element iOS Currently the Element mobile apps do not support custom Jitsi servers and will instead use the default `jitsi.riot.im` server. When users on the mobile apps join the call,