-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nice read #12
Comments
👍 That is a good read thanks for posting it - I'll cross-post it to the https://gitter.im/rtc-io/discuss page too. One thing that definitely stood out that hasn't been highlighted before is the importance of encryption during signalling. I think for this reason, I'll move to specifying the default signalling server as |
I love these diagrams. But I think there's an unnecessary dependency on Bob's end. He doesn't have to wait with getusermedia until he has received a connection request. |
Sounds like the author is looking for feedback and happy to make corrections |
Yeah, and thanks for moving to crypto by default! |
Yeah, not sure how to give him feedback - there are no comments on the blog post. :-( |
emailed them at info@ - let's see what they say. |
https://www.pkcsecurity.com/blog#webrtc-flow
This is a great resource, just wanted to share it
The text was updated successfully, but these errors were encountered: