5 ms·
Sad to see this is dependent on an extension to WebRTC that’s (currently) Chrome / Chromium-only. It’s still a proposed API, and I don’t see when this will be s
by christefano 6y ago
Sad to see this is dependent on an extension to WebRTC that’s (currently) Chrome / Chromium-only. It’s still a proposed API, and I don’t see when this will be supported by any other browsers.
- garmaine 6y agoReally, really sad. I’m not going to run Chrome for this one application.
- sigwinch28 6y agoI'm not sure if you are aware of the difference, but you can use Chromium instead of Chrome. I am mainly a Firefox user on NixOS, but for running Chrom{e,ium} I find that Firejail [0] is a good option. For example, to run chromium in "store" mode and point it to the demo jitsi instance: firejail --profile=chromium chromium --app="https://meet.jit.si" In reality, I combine this with `nix-shell` and set it as a shell alias, since Chromium isn't something I use regularly: nix-shell -p chromium --run "firejail --profile=chromium chromium --app=\"https://meet.jit.si\"" The `--app` option removes browser controls, so it almost behaves like an Electron application. [0]: https://github.com/netblue30/firejail https://github.com/netblue30/firejail
- barbs 6y agoOr you can download the Electron app here https://github.com/jitsi/jitsi-meet-electron https://github.com/jitsi/jitsi-meet-electron
- sigwinch28 6y agoDidn't realise they had one! Might be more convenient than my shell aliases :)
- garmaine 6y agoI’m not going to run a different browser for one application. I don’t even install anything derived from Chrome in my computer, and I’m not going to change that policy.
- sigwinch28 6y agoFair enough. Please be aware that aside from E2E demoed here, there is allegedly a Firefox-specific bug regarding WebRTC which degrades performance for all participants in a call: https://community.jitsi.org/t/software-unusable-on-firefox-why/22143 https://community.jitsi.org/t/software-unusable-on-firefox-w...
- elric 6y agoSeems like Jitsi relies on Chrom(e|ium) for a lot of things. Desktop sharing? Chrome plugin. Desktop client? Chromium/Electron. I tried setting up an instance for my company to replace zoom, but I can't go around demand that people install any particular browser.
- saghul 6y agoThat is not really true. Yes, our Firefox support has not been great, but we are working on making it better: https://github.com/jitsi/jitsi-meet/issues/4758 https://github.com/jitsi/jitsi-meet/issues/4758 > Desktop sharing? Chrome plugin. This was a browser limiation, which is no longer needed since about 2 years ago. > Desktop client? Chromium/Electron. You need to ue it! Use the browser, or the mobile apps.
- elric 6y agoJitsi Meet even shows a popup saying Firefox is not supported, and the only fully supported browsers are Chrome and Chromium. You're right that screen sharing does seem to work in Firefox! Thanks for pointing that out. It looks like FF on my Linux box is blocking it, but I guess that's a permission issue I need to fix locally.
- saghul 6y agoIt is our belief that by doing this we'll also be helping adoption. If a browser vendor (any of them) propoes an API, but nobody uses it, why would the rest care to implement it? The ability to do E2EE is kind of a big deal, even though insertable streams can be used for other things, so we hope other browser vendors join the effort. There have been other approaches in the past such as PERC [0] and ongoing related ones like MLS [1], this is a relevant topic these days. [0]: https://datatracker.ietf.org/group/perc/documents/ https://datatracker.ietf.org/group/perc/documents/ [1]: https://datatracker.ietf.org/wg/mls/about/ https://datatracker.ietf.org/wg/mls/about/