Live data from Hacker News

Show HN: Create a WebRTC service in less time than it takes to install Skype

vline.com

11–14 of 14 posts

Re: Show HN: Create a WebRTC service in less time than it takes to install Skype

#11

A bit of a side note, but how does WebRTC integrate with Twilio Client? Twilio Client was modified to use WebRTC as an alternative to the original Twilio Client, which integrated with Flash to connect calls. Introduction here ( http://www.twilio.com/blog/2012/11/webrtc-for-twilio-client-... ) And how does your product differ from Twilio Client?

I can't speak to how the Twilio Client works, but how we're different is easy: We do video. Twilio is only voice.

Re: Show HN: Create a WebRTC service in less time than it takes to install Skype

#13
post #5
post #4

Nice start, but some criticisms: - This just seems like a wrapper around webrtc, with some presence stuff thrown in. - Your website does not mention anywhere that the majority of web users do not support webrtc http://caniuse.com/#feat=stream - Is this a product? Why would I use this? Are you actually aiming at replacing skype? If not, why target it in your slogan? Do you intend on having users embed it in their site…

Good feedback. To address your comments: >> This just seems like a wrapper around webrtc, with some presence stuff thrown in. It turns out there is quite a bit of server-side infrastructure required to support webrtc apps. The biggest ones being relay, STUN, and signaling servers. Operating these yourself is non-trivial, especially if you want good performance around the world. We also have a pretty full-featured cha…

Signaling isn't really that hard, and I say that as someone who wrote a signaling and chat server for webrtc. Fortunately, the chat server is no longer necessary and that functionality can ride on webrtc itself. (And I assume you didn't write your own STUN server and are just hosting/running an existing one.)

Do you run a TURN server?

Re: Show HN: Create a WebRTC service in less time than it takes to install Skype

#14
post #5

Earlier quoted context omitted.

Good feedback. To address your comments: >> This just seems like a wrapper around webrtc, with some presence stuff thrown in. It turns out there is quite a bit of server-side infrastructure required to support webrtc apps. The biggest ones being relay, STUN, and signaling servers. Operating these yourself is non-trivial, especially if you want good performance around the world. We also have a pretty full-featured cha…

Signaling isn't really that hard, and I say that as someone who wrote a signaling and chat server for webrtc. Fortunately, the chat server is no longer necessary and that functionality can ride on webrtc itself. (And I assume you didn't write your own STUN server and are just hosting/running an existing one.) Do you run a TURN server?

Not sure what to say about signaling other than handling all the edge cases takes a non-trivial amount of effort and testing (which is true of most things in software).

Chat is only possible peer-to-peer if you don't care about histories. Since losing your history every time you reload a page or close a tab isn't a great experience, it's helpful to have a server in the middle keeping the history, unread counts, etc (which we do support today). Presence will always require a server.

We do run relay and STUN servers in locations around the world. Our STUN server is based on an open source implementation, but it is substantially customized. The relay server is our own.

Post reply on HN