We are, unfortunately, somewhat at the mercy of the browser's implementation of WebRTC APIs when it comes to negotiating a connection. If the browser fails to get the candidates required to identify a peer-to-peer connection, then you might see the sort of behaviour you observed with Safari.
That said - I'm not convinced it's solely browser dependent. I use Safari among other browsers, and I have not noticed an appreciable difference in peer-to-peer connection success rates versus the other browsers. It may be that your environment has additional confounding variables that cause Safari to behave poorly.
I'm also on Safari 17.5.
That said - I'm not convinced it's solely browser dependent. I use Safari among other browsers, and I have not noticed an appreciable difference in peer-to-peer connection success rates versus the other browsers. It may be that your environment has additional confounding variables that cause Safari to behave poorly.
I'm also on Safari 17.5.
Statistics: Posted by tdewey — Tue Jul 23, 2024 10:54 am