Synapse: homeserver.yaml variable to specify self hosted jitsi-server
As per subject.
For privacy and to take load off public jitsi-meet servers.
zaggynl
👍5
😕1
All 2 comments
I'd say most correct place would be client .well-known, so every client (that supports Jitsi-stuff at all) would know what to do, as Jitsi is still after all client widget more than homeserver feature as is... But in any way, some method for clients to know what Jitsi server to use, that doesn't require configuring client config itself, which is impossible for mobile clients and so on.
olmari
on 28 Mar 2020
👍5
closing this in favour of https://github.com/matrix-org/matrix-doc/issues/2488. We'd need to figure out how/if this would fit into the matrix protocol before it could be implemented in synapse.
richvdh
on 6 Apr 2020
Was this page helpful?
0 / 5 - 0 ratings
Related issues
brainscar
路
3Comments
WGH-
路
4Comments
APwhitehat
路
4Comments
clokep
路
4Comments
MurzNN
路
5Comments
Most helpful comment
I'd say most correct place would be client .well-known, so every client (that supports Jitsi-stuff at all) would know what to do, as Jitsi is still after all client widget more than homeserver feature as is... But in any way, some method for clients to know what Jitsi server to use, that doesn't require configuring client config itself, which is impossible for mobile clients and so on.