I am also biased and would prefer to blame the browsers when things go wrong. But, it is equally wrong to blame browsers when they are not at fault. Jitsi has rolled out changes that broke first Chromium (still not fixed) and then Firefox (fixed for me, but apparently not everyone). My browsers did not change. (Yes, I checked the change logs.)
I run the “stable” version of Debian GNU/Linux which comes with stable browsers which do not get updated except for security patches. You may have noticed that my Firefox version number is not 95, it is 78. Likewise, I’m running Chromium 90 and have been since April. It worked for months with Jitsi Meet until around Halloween when it started exploding with an instant “Oh Snap!” error as soon as someone else joins the room.
I was told that the WebRTC crashes do not occur in the latest Chrome/ium. That’s not a workable solution for me, so my plan has been to just use Firefox ESR until the bug gets fixed.
And, for a while, Firefox was actually better. Jitsi Meet had been crashing daily on both Google Chrome and Chromium on my machine if I leave a room open with only myself in it. I believe it was triggered by a new participant joining, but I do not know. Firefox has had no such problem. I’ve had a room open for days, with occasional visitors, and it has been rock solid. (Well, other than the known bugs with screensharing not re-enabling the video and having to reload; but I’m pretty sure that is a browser issue.).
I do not like to complain about such a great product, but I do want to give constructive feedback. I wish I knew better how to debug Jitsi so that, even if I can’t fix the bugs, at least I could report them in a helpful and reproducible way. Is there documentation somewhere? I’d enjoy reading a Jitsi Meet Debugging How To or watching a video of developers tracking down a bug in the JS Console while they talk aloud what they are thinking. Does anything like that exist, @damencho?