Oh don't let me get me started on this. I use Firefox on a work machine and I spent a number of hours troubleshooting why it couldn't access the Internet when I was connected on VPN.
I suspected it had something to do with snapd, so I downloaded the .tar.gz release of Firefox and it worked. I kept investigating and figured it must have something to do with snap.firefox.firefox apparmor profile because the VPN client was symlinking the /etc/resolv.conf to /opt/.../resolv.conf
However, updating the apparmor profile didn't help so I ultimately realized that snap has a hardcoded list of paths that get mounted into the app container [1] and there's no way to change this.
There are a number of reasons to hate on snapd, but this almost made me flip the table.
Also, as a bonus point, if you look at the apparmor profile I mentioned it has a ton of comments about chrome, so someone must've just copy pasted it and modified to work with Firefox. GrEaT SeCuRiTy!
I hear you, I've been working on peercalls.com, a video conferencing app, for the past few years and it works on all major browsers and platforms, including Firefox.
That said, I'm bummed out that E2EE using insertable streams / SFrame transform is only currently supported in Chrome.
I've also noticed that very few devs in the WebRTC community actually test stuff in Firefox.
I've been developing Peer Calls since 2016. It's an open source WebRTC group conferencing solution, doesn't require a user account, has a full-mesh P2P and SFU mode (streaming through central server). Works on Android, iOS, Firefox, Chrome, Safari, latest Edge and there is no app - only a link that you need to share: https://peercalls.com/
I don't like that I have to use their web player to listen to music. Also if their licensing deals change, the music that used to be there can disappear. I don't like that and therefore I continue to support bands via Bandcamp, from where I can download FLAC files. Unfortunately not all bands are there and some keep focusing on streaming platforms/YouTube and it's becoming harder and harder to get the music files locally.
Author of Peer Calls here, an open source, anonymous WebRTC multi-user conferencing solution. I recently ported the app that Go and added an SFU (thanks to pion/webrtc) to make support for 3+ users better. Works on all recent major browsers (including Safari on iOS).
I suspected it had something to do with snapd, so I downloaded the .tar.gz release of Firefox and it worked. I kept investigating and figured it must have something to do with snap.firefox.firefox apparmor profile because the VPN client was symlinking the /etc/resolv.conf to /opt/.../resolv.conf
However, updating the apparmor profile didn't help so I ultimately realized that snap has a hardcoded list of paths that get mounted into the app container [1] and there's no way to change this.
There are a number of reasons to hate on snapd, but this almost made me flip the table.
Also, as a bonus point, if you look at the apparmor profile I mentioned it has a ton of comments about chrome, so someone must've just copy pasted it and modified to work with Firefox. GrEaT SeCuRiTy!
[1]: https://github.com/snapcore/snapd/blob/3a88dc38ca122eba97192...