[ianbooker]

Looks good. But does it scale?

And Firefox is not supported?

[mordae]

Why is this downvoted?

Anyway, this open source alternative doesn't work with the open source browser and suggests to install two proprietary ones instead.

[fmeringdal]

> And Firefox is not supported?

Sorry about that! I had actually commented out firefox support in the frontend, but I pushed a new updated now that uncommented it.

Firefox is supported

[blueblob]

Maybe the demo server needs to be restarted, because it still does not work.

[fmeringdal]

I forgot to update the demo :) Now it works

[mfkp]

You should consider allowing Edge browser as well (since it's based on Chromium anyway, I imagine it should work fine).

[fmeringdal]

I thought Edge was supported but I havent tested it. This is a list of the browsers that are supported: https://github.com/fmeringdal/nettu-meet/blob/main/frontend/....

Are you running an old version of edge? If not, do you mind filing a issue in the repository?

[mfkp]

Ah, that must be the issue. I'm using Edge on Linux (I know, it's weird).

I'll go ahead and file an issue for it now :-)

[fmeringdal]

It is not horizontally scalable right now, but that is not hard to implement either. You can have a look at the dogehouse project: https://github.com/benawad/dogehouse if you want to see how to horizontally scale mediasoup which is the media handler and stateful process within the servers.

I think vertical scaling will be more than enough for most of the users that are going to self-host this.

[lhoff]

What would you say is the maximum of users in a single session if everyone has Video sharing activated.

[marsouin]

I was wondering the same thing. How scalable is it? Any recommendations for deployment/production use?

[pmontra]

Yep, I wonder what are the technical reasons not to support Firefox. Some missing codec as (maybe) for the lack of support in FaceTime web?

[kwindla]

Firefox WebRTC support isn't missing anything big, but it's missing a lot of little things from the 1.0 spec that Chrome (and, increasingly, Safari) have. But, much worse from a support perspective, recent Firefox releases have been fairly likely to have WebRTC-related breaking changes and regressions.

We all try to support Firefox. But given the relative usage numbers of Firefox, Chrome/Chromium/Electron/Edgium, and Safari, it's sometimes hard to devote resources to testing and workarounds.