diff options
| author | Adam Spiers <github@adamspiers.org> | 2021-03-14 14:04:24 +0000 |
|---|---|---|
| committer | Saúl Ibarra Corretgé <s@saghul.net> | 2021-03-14 15:34:20 +0100 |
| commit | b41de51ed25375acb526690c716ffbe7b41ec7d7 (patch) | |
| tree | 73805f55fe9835e2b9ffaf582204e7a6b8341e8f | |
| parent | ce2243d220566b46ccbf9ac6aa45481316a75acc (diff) | |
README: explain why remote control was disabled
Just marking the remote control feature as disabled without explaining why
was not at all helpful to end users needing this feature. So link to a couple
of pages to help them understand the reasoning. It may even attract
developers to work on a fix.
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -9,7 +9,7 @@ Desktop application for [Jitsi Meet] built with [Electron]. - [End-to-End Encryption](https://jitsi.org/blog/e2ee/) support (BETA) - Works with any Jitsi Meet deployment - Builtin auto-updates -- ~Remote control~ (currently disabled) +- ~Remote control~ (currently [disabled](https://github.com/jitsi/jitsi-meet-electron/issues/483) due to [security issues](https://github.com/jitsi/security-advisories/blob/master/advisories/JSA-2020-0001.md)) - Always-On-Top window - Support for deeplinks such as `jitsi-meet://myroom` (will open `myroom` on the configured Jitsi instance) or `jitsi-meet://jitsi.mycompany.com/myroom` (will open `myroom` on the Jitsi instance running on `jitsi.mycompany.com`) |