- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Feb 2019 17:19:35 +0000
- To: public-webrtc-logs@w3.org
> Sure. It's a collaborative screenwriting SPA with about 25,000 weekly users. When editing a script in eg Google Drive, users form WebRTC p2p edit-groups (websocket signalling, Operational Transform based editing, and a RAFT-based leader system for conflict control). It works great, just not for same-building Safari users (or Edge users, of course, but I'll worry about that once Edge gets above 0% on caniuse.com). Does it mean that Safari is not supported at all? Do you fallback on Web Socket? What about TURN, too slow, too costly? It would be great if you are in a position to share connection success stats. Safari Tech Preview has support for mDNS ICE candidates which should improve Safari-to-Safari connection rate. > someone doing an 'adult' stream might want to share their camera but would _never_ want to give away their location Chances are their location is already given fairly accurately by their public IP address that are already exposed by regular web browsing. I tend to think that host candidates are more used for tracking/fingerprinting users. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2012#issuecomment-462413874 using your GitHub account
Received on Monday, 11 February 2019 17:19:36 UTC