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'm the creator of Peer Calls [1], a peer to peer video conferencing web app using WebRTC, and it has a basic chat functionality (sending files is a little quirky). The first release was back it in 2016. Users create a room and share the link.
It's built in NodeJS/React/TypeScript, and I just recently ported the backend to Go because I wanted to build a Selective Forwarding Unit using pion/webrtc. You can test this in the alpha release on peercalls.com/alpha [2].
Would love to get more feedback and/or bug reports! Open source, available on
GitHub [3].
I discovered Peer Calls last night and think it’s an awesome project! It worked flawlessly from both my phone and desktop; it’s one of the (surprisingly few) fully featured WebRTC chat apps!
My one hope: Could it be possible to select from different audio bitrates when on a direct connection? High bandwidth audio seems like one of the huge selling points of P2P chat applications. My naive assumption is that it’s the sampleRate constraint on the audio stream, but I’m not sure how the compression works...
I've been developing peercalls.com on and off on since 2015. It's an open source peer to peer WebRTC audio/video calling service, allows the users to chat, share their desktop and send files (sending files is a little buggy at the moment, works best in Firefox).
It has gotten a lot of interest in the past month and I noticed a spike in web traffic so I'm actively working on making it more scalable. I'm planning on implementing an SFU to support calls with more than 3-4 people. Right now the peers establish a mesh network and it quickly gets expensive to send video to more users.
I've also been paying attention to the criticisms of Zoom and other WebRTC conferencing services and am hoping to implement end to end encryption for intermediate servers using Insertable Streams once the functionality is supported in most browsers.
Thanks for sharing. It doesn't seem to work well in Safari on desktop or iOS. Seemed to connect but if you make the video larger than thumbnail or fullscreen it either doesn't show or only displays a small sliver.
Thanks for reporting the bug! I thought I'd fixed this issue. Which version of MacOS/iOS/Safari are you using?
Edit: I just realized that I just hadn't pushed the latest version which contained this fix. v3.0.17 is up and running now (was v3.0.15). Please let me know if you continue to experience this or any other issue!
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...