3 ms·
Unfortunately, that's the case: Safari and Firefox haven't yet implemented WebRTC Insertable Streams, which we use for end-to-end encryption. And on iOS even Ch
by barathr 4y ago
Unfortunately, that's the case: Safari and Firefox haven't yet implemented WebRTC Insertable Streams, which we use for end-to-end encryption. And on iOS even Chrome is not really based on chromium (due to Apple's restrictions). We know support for the latest WebRTC standards is on the roadmap for Firefox (not sure about Safari).
So for the time being we support chromium based browsers (Chrome, Vivaldi, Brave, Edge, etc.).
- HappyTypist 4y agoI think you need to work on iOS support, or this will not take off. P.S. Beautiful project for a problem that definitely needs solving.
- barathr 4y agoThanks! We're thinking through the right architecture; it's a question of whether WebKit will get Insertable Streams soon enough, or if we'll need to create a custom client. Our preference is for users to not need a custom client, because that's one more piece of software they need to keep up to date.