pthatcherg

10 ms·

61.
by pthatcherg 7y ago
It is possible to have conference calls with e2e encryption. Many conference calls are implemented using what's called a Selective Forwarding Unit (SFU) and the sending clients send multiple resolutions (either independent, called &quo
62.
by pthatcherg 7y ago
As far as I know, there's nothing special about telehealth that prevents it from using e2e encryption.
63.
by pthatcherg 7y ago
There are 2 different kinds of video calls: 1:1 and group calls. For 1:1 calls, e2e encryption incurs negligible processing and bandwidth. Do you worry about the processing and bandwidth increase when using HTTPS/SSL? Probably not.
64.
by pthatcherg 7y ago
First of all, there are 2 different kinds of video calls: 1:1 and group calls. For 1:1 calls, e2e encryption doesn't cause any problem at all. For group calls, it depends on how it's implemented, but many group calls are implemen
65.
by pthatcherg 7y ago
I haven't used the desktop Signal app, but there appears to be one: https://signal.org/download/
66.
by pthatcherg 8y ago
https://w3c.github.io/webrtc-quic/ is "outside" of webrtc in the sense that it doesn't use PeerConnection and doesn't require signaling. But it currently doesn't require some form of ICE (not
67.
by pthatcherg 8y ago
At TPAC last week the WebRTC WG decided to adopt the spec, although it needs to be verified on the mailing list, as there were some members present not in favor of adopting it. (I'm an editor of the document and am in favor of it).
68.
by pthatcherg 8y ago
You can do the same with QUIC streams (size them appropriately and get a 1:1 mapping with UDP packets).
69.
by pthatcherg 8y ago
It's been there for years and they've been steadily improving it. If anything, it will keep getting better, not go away.
70.
by pthatcherg 8y ago
(I work at Google, on Chrome) I know both people from both the MSE team and the Project Stream team. Project Stream doesn't use MSE (it uses WebRTC) and the code in Chrome to detect live streams and optimizing them has been around lo
71.
by pthatcherg 9y ago
As I just commented higher up in the thread, it is possible to force UDP if that's what you want. And while WebRTC is complex, you can ignore almost all of that if you're just doing client to server data channels. You just need t
72.
by pthatcherg 9y ago
I've already commented at length about this, but I'll repeat: UDP without congestion control in browsers is not really an option. UDP with congestion control is basically what QUIC is. So we might as just get p2p QUIC connection
73.
by pthatcherg 9y ago
You can cause effectively force UDP by doing two things: 1. Don't signal TCP ICE candidates. 2. Don't provide TCP TURN servers. If you do those two things, it's impossible to get a TCP connection. In fact, just doing #2 wi
74.
by pthatcherg 10y ago
You don't need to give a server. It works fine with just host ICE candidates from the server and no stun or relay candidates.
75.
by pthatcherg 10y ago
(Member of the Google WebRTC team here) We are aware that it's a pain to use just the data channel, and we're working on it. We're refactoring the native API to be more ORTC-like and make it possible to compile without all t
76.
by pthatcherg 10y ago
You need to implement DTLS and SCTP for client->server, just not ICE. But client->server ICE is fairly trivial with ICE lite. It's DTLS+SCTP that are complex, and they don't go away client->server. Replacing DTLS+SCTP w
77.
by pthatcherg 10y ago
Are you using the data channel p2p or client-to-server? (I work on WebRTC and implemented much of the data channel; I'm always interested when someone uses it)
78.
by pthatcherg 10y ago
QUIC Crypto design doc: https://docs.google.com/document/d/1g5nIXAIkN_Y-7XJW5K45IblH...
79.
by pthatcherg 10y ago
You can receive data messages our of order. That's all there is to it. If you could receive TCP out of order, you could just use TCP.
80.
by pthatcherg 10y ago
Indeed, I misread your comment. Well, hopefully in the future how I read the comment will be correct. I don't think it would be that hard to write a data-channel-only server using BoringSSL and usrsctplib. See a comment of mine furt
81.
by pthatcherg 10y ago
Which API? PeerConnection? Would you prefer an API like ORTC?
82.
by pthatcherg 10y ago
If you want to force all traffic through a proxy, you must enable it using an extension, such as this one: https://chrome.google.com/webstore/detail/webrtc-network-lim...
83.
by pthatcherg 10y ago
There was a discussion about this on go-nuts: http://grokbase.com/t/gg/golang-nuts/161wbn1vf0/go-nuts-nati... There are two bindings for Go built on top of the WebRTC code at webrtc.org: https:/&#x
84.
by pthatcherg 10y ago
Hi, I'm a member of the WebRTC team at Google, and I wrote a lot of the data channel and network code that's part of that behemoth. I'm glad you got this to work :). I've always hoped someone would do exactly what you&#
85.
by pthatcherg 11y ago
The WebRTC implementation found at webrtc.org, which is used by Chrome, can also be used by mobile apps, including iOS. It's BSD licensed and used by many mobile apps. (I work on the WebRTC team)
86.
by pthatcherg 11y ago
What kind of an RTC API would you like to see?
87.
by pthatcherg 11y ago
You can control WebRTC's network behavior, including forcing it to go through a proxy, by using this Chrome extension: https://chrome.google.com/webstore/detail/webrtc-network-lim... It's published by th
88.
by pthatcherg 11y ago
Member of the WebRTC team here. If you go read the bug you linked to, you can see that we added code to Chrome to specifically make this extension possible. It's in many CLs, but here is an example of one: https://chromium.
89.
by pthatcherg 11y ago
For access to the mic and camera, that's basically what it does already: prompt for permission. So what you're really asking for is "can the web app know my non-NATed IP address if I'm behind a NAT and my non-VPN IP addr
90.
by pthatcherg 11y ago
I know that one big deal is fewer round trips. DTLS+SCTP requires several round trips to establish a secure connection (around 4 I think). DTLS 1.3 should improve that on the DTLS side of things, but QUIC is designed from the beginning to

More ›