Live data from Hacker News

Twilio Video – Real-time WebRTC video infrastructure

twilio.com

1–10 of 106 posts

Re: Twilio Video – Real-time WebRTC video infrastructure

#4
I was really excited by the title but this seems a bit lacking.

I've done a lot of WebRTC work -- we currently use Google Hangouts everywhere at Stack Exchange for internal team communication, but the 15 person cap hurts some bigger all-hands calls or our weekly remote parties. I don't think the hardest part of WebRTC is transcoding or TURN servers (what Twilio seems to be offering), multiplexing is where all the complexity comes from.

It's very easy to set up a video chat interface via WebRTC small-scale, and good on Twilio for focusing on making it easier to integrate mobile clients too, but I can't wait until someone (most likely the Talky.io team seeing how their betas are going) makes it a bit easier to have large N connections (right now on Hangouts N is 15, on my own stack N is around 10).

Re: Twilio Video – Real-time WebRTC video infrastructure

#5
post #4

I was really excited by the title but this seems a bit lacking. I've done a lot of WebRTC work -- we currently use Google Hangouts everywhere at Stack Exchange for internal team communication, but the 15 person cap hurts some bigger all-hands calls or our weekly remote parties. I don't think the hardest part of WebRTC is transcoding or TURN servers (what Twilio seems to be offering), multiplexing is where all the com…

Interesting, is the 15 person cap a new thing? I remember it was still 10 at some point.

Re: Twilio Video – Real-time WebRTC video infrastructure

#6
post #4

I was really excited by the title but this seems a bit lacking. I've done a lot of WebRTC work -- we currently use Google Hangouts everywhere at Stack Exchange for internal team communication, but the 15 person cap hurts some bigger all-hands calls or our weekly remote parties. I don't think the hardest part of WebRTC is transcoding or TURN servers (what Twilio seems to be offering), multiplexing is where all the com…

Large conferences translates to media server, network, sometimes interop, and eventually session control requirements.

Ideally, media servers with excellent IP connections, distributed around the world, and behind GeoDNS.

It also often means some interop capabilities (signaling and/or media interworking), since many large conference use cases include some users on traditional video (SIP or H.323), Lync/Skype For Business and/or PSTN.

Finally, session control becomes important if we get into enterprise and service provider conferencing markets.

Those reqs - especially media intensive ones - are interesting in that they are mostly not Twilio's core competency. Do they build it? Partner for it? Do they care enough about those use cases?

The answers to those questions are very interesting given Twilio's tremendous developer ecosystem.

Re: Twilio Video – Real-time WebRTC video infrastructure

#7
post #5
post #4

I was really excited by the title but this seems a bit lacking. I've done a lot of WebRTC work -- we currently use Google Hangouts everywhere at Stack Exchange for internal team communication, but the 15 person cap hurts some bigger all-hands calls or our weekly remote parties. I don't think the hardest part of WebRTC is transcoding or TURN servers (what Twilio seems to be offering), multiplexing is where all the com…

Interesting, is the 15 person cap a new thing? I remember it was still 10 at some point.

I think it is 10 for ad-hoc Hangouts, but you can raise it to 15 if you attach the meeting to a calendar invite.

Re: Twilio Video – Real-time WebRTC video infrastructure

#8
The support for H.264 is interesting.

It of course makes sense for iOS and devices that can support hardware acceleration, but device mix can change during a call. So, what happens if two iOS users start, but then they add a VP8 only device? How Twilio handles that use case will be instructive for understanding what use cases we can support with this service.

It isn't likely they are transcoding since this intro suggests a P2P architecture without distributed media servers, and we know H.264/VP8 is very expensive video transcoding - e.g. many media server vendors don't get more than one transcode per core at full HD.

Re: Twilio Video – Real-time WebRTC video infrastructure

#9
> Provides multi-party authentication, registration and signaling, which can orchestrate up to 4-way calling using peer to peer mesh topology, across any combination of supported devices. Calls can be video or voice only.

Peer to peer mesh topology? Anyone know of further reading on this?

Re: Twilio Video – Real-time WebRTC video infrastructure

#10
post #9

> Provides multi-party authentication, registration and signaling, which can orchestrate up to 4-way calling using peer to peer mesh topology, across any combination of supported devices. Calls can be video or voice only. Peer to peer mesh topology? Anyone know of further reading on this?

"up to 4-way calling using peer to peer mesh topology" sounds like fancy names for regular WebRTC connections.
Post reply on HN