4 ms·

We tried to but with most of our team on Firefox it simply doesn't work unfortunately. Zoom has been the only thing reliable for us. It's a bit ironic that som

We tried to but with most of our team on Firefox it simply doesn't work unfortunately. Zoom has been the only thing reliable for us. It's a bit ironic that somewhere, someone is switching from Firefox to Chrome because of data concerns with Zoom.

passerby1 7y ago
What does prevent your team from using "ungoogled chromium"?
ooboe 7y ago
That's odd. My experience with Firefox on Windows is that I can't get audio to work with Zoom. Jitsi, on the other hand, works perfectly though there is a small yellow box that warns me that I should use a "fully supported browser"
- flas9sd 7y ago
  in Zooms webclient for audio to work with Firefox you'll need current Nightly, staged to be released as version 76 in May. Edit: another poster linked the bugzilla issue for AudioWorklets
- Certhas 7y ago
  We use the Zoom standalone mostly. So Firefox isn't involved in the Zoom side. Jitsi works fine with small groups. But if we have >10 Firefox users in a room it doesn't for us. Maybe if you have much better internet than we have or otherwise better resources it works for you? We were using a WebRTC based tool before Corona (DFN), and had deprecated Zoom, unfortunately the people running that didn't manage to scale it up sufficiently in the crisis, hence we had to fallback to Zoom.
- fulafel 7y ago
  Anyone know what the reason for the yellow box is?
  - Certhas 7y ago
    Because Firefox in Jitsi is seriously not working unless you have small groups and resources to spare. But they are working on it: https://github.com/jitsi/jitsi-meet/issues/4758 https://github.com/jitsi/jitsi-meet/issues/4758 https://github.com/jitsi/jitsi-meet/issues/5439 https://github.com/jitsi/jitsi-meet/issues/5439
    - fulafel 7y ago
      Does it need more bandwidth or more server resources (or both?)
jdc 7y ago
Have you tried BigBlueButton?
nerpderp82 7y ago
I am on ubuntu 18.04 lts using firefox and jitsi hard locked my machine, it was still sending packets, but all UI was frozen, I had to power cycle the machine. On osx using chrome, it was flawless.

passerby1 7y ago

What does prevent your team from using "ungoogled chromium"?

ooboe 7y ago

That's odd. My experience with Firefox on Windows is that I can't get audio to work with Zoom. Jitsi, on the other hand, works perfectly though there is a small yellow box that warns me that I should use a "fully supported browser"

flas9sd 7y ago
in Zooms webclient for audio to work with Firefox you'll need current Nightly, staged to be released as version 76 in May. Edit: another poster linked the bugzilla issue for AudioWorklets
Certhas 7y ago
We use the Zoom standalone mostly. So Firefox isn't involved in the Zoom side. Jitsi works fine with small groups. But if we have >10 Firefox users in a room it doesn't for us. Maybe if you have much better internet than we have or otherwise better resources it works for you? We were using a WebRTC based tool before Corona (DFN), and had deprecated Zoom, unfortunately the people running that didn't manage to scale it up sufficiently in the crisis, hence we had to fallback to Zoom.
fulafel 7y ago
Anyone know what the reason for the yellow box is?
- Certhas 7y ago
  Because Firefox in Jitsi is seriously not working unless you have small groups and resources to spare. But they are working on it: https://github.com/jitsi/jitsi-meet/issues/4758 https://github.com/jitsi/jitsi-meet/issues/4758 https://github.com/jitsi/jitsi-meet/issues/5439 https://github.com/jitsi/jitsi-meet/issues/5439
  - fulafel 7y ago
    Does it need more bandwidth or more server resources (or both?)

jdc 7y ago

Have you tried BigBlueButton?

nerpderp82 7y ago

I am on ubuntu 18.04 lts using firefox and jitsi hard locked my machine, it was still sending packets, but all UI was frozen, I had to power cycle the machine. On osx using chrome, it was flawless.