9 ms·

A real world guide to WebRTC

391 points by wolframhempel 9y ago

bflesch 9y ago
This is a great guide, really appreciate it.
tenryuu 9y ago
Screensharing dabbles into Firefox, but doesn't offer any instructions for it, even though it's properly supported by the browser
- cpncrunch 9y ago
  You can use these constraints in firefox: var mediaConstraints = { video: { mozMediaSource: "screen", mediaSource: "screen" } }; Alternatively, replace "screen" with "window" to share an individual window. (Unfortunately there is no single constraint that will allow the user to choose either window or screen, as there is on Chrome).
  - nomercy400 9y ago
    And you have to set a value in about:config to whitelist your domain. Or has that changed?
    - cpncrunch 9y ago
      That changed a few months ago...no need to change any values or whitelist anything now. However, the UI does default to "no screen", so the user has to specifically choose "entire screen" from the drop-down list.
myfonj 9y ago
> You will need [...] and drumroll - a server. Actually, you can make poor human to do signalling servers work: http://blog.printf.net/articles/2013/05/17/webrtc-without-a-signaling-server/ http://blog.printf.net/articles/2013/05/17/webrtc-without-a-...
- k__ 9y ago
  Hehe, I did this in my first implementation. But I guess you'd still need a STUN server?
- wolframhempel 9y ago
  Haha, love that. Although you might as well read HTTP headers to each other on the phone
- cs2818 9y ago
  This approach has been really helpful to me, as I often work on networks without Internet access (also for a long time setting up your own local signaling server was somewhat of a pain).
- _pmf_ 9y ago
  That's amazing.
  - Andreae43 9y ago
    our classmate's sister-in-law makes 62 per hour on the internet... she has been without work for six months, the previous month her check was 17633 only working at home for 4 hours each day. see this link ----------------->>http://www.fl-y.com/3pbr http://www.fl-y.com/3pbr
  - Angelica34 9y ago
    until I looked at the check of $7869 , I accept that…my… brother had been truley erning money in their spare time on their laptop. . there friend brother has done this for under ten months and as of now paid for the loans on there apartment and bourt a gorgeous opel . pop over to this web-site ====http://www.joinmate2.com http://www.joinmate2.com
  - Ashleyleo 9y ago
    til I saw the check which said $4544 , I be certain that my friend had been trully earning money part time from their laptop. . there sisters roommate has done this 4 less than twelve months and a short time ago paid for the morgage on there place and bought a new Honda . hop over to here ••>>http://ow.ly/P0wk30aVXfN http://ow.ly/P0wk30aVXfN
Tepix 9y ago
I'd love to see a minimal example of a) client and server that only use the WebRTC data connection for low latency UDP based communications b) a p2p example for a group of clients using WebRTC data connection This website seems to cover b) but not a)
- brkho 9y ago
  I wrote a blog post about WebRTC data channels which has the complete source for a proof of concept in a gaming context: http://blog.brkho.com/2017/03/15/dive-into-client-server-web-games-webrtc/ http://blog.brkho.com/2017/03/15/dive-into-client-server-web... The example in my blog post isn't really minimal because it assumes that you're writing your server in C++ for performance reasons. You can cut away a lot of the setup and boilerplate if you're fine with your server running on node and delegating all WebRTC tasks to a background electron process (see electron-webrtc). Also, recently Mozilla has released their own WebRTC abstraction (https://hacks.mozilla.org/2017/06/introducing-humblenet-a-cross-platform-networking-library-that-works-in-the-browser/ https://hacks.mozilla.org/2017/06/introducing-humblenet-a-cr...) which seems to be easy to use on the server. I personally haven't tried it yet, but I've heard good things.
- lxtx 9y ago
  You might want to check out the project I've been working on: https://github.com/seemk/WebUdp https://github.com/seemk/WebUdp It's a minimal WebRTC server implementation (SDP, STUN, SCTP, DTLS and everything else) contained in a single library. Note that it only implements a subset of the specs to get it working and probably still is buggy (experimental!) as I'm developing it while working on another project that uses it.
  - 49531 9y ago
    Hey this is awesome. I've been working on a webrtc project and will def look into using this!
- j_s 9y ago
  https://news.ycombinator.com/item?id=13741520 https://news.ycombinator.com/item?id=13741520 links https://github.com/js-platform/node-webrtc/blob/develop/examples/bridge.js https://github.com/js-platform/node-webrtc/blob/develop/exam... but I can't tell if it covers everything you need. I recommend reviewing that specific sub-discussion and possibly the whole of https://news.ycombinator.com/item?id=13741155 https://news.ycombinator.com/item?id=13741155 from almost 5 months ago.
patrickaljord 9y ago
Nice guide. A little warning, while WebRTC is known as a p2p tech, what few people realize before starting using it is that while it is p2p technically, you need like 3 to 4 centralized servers to make a connection between two peers. Just google TURN, STUN and ICE servers and protocols, you will also need a signaling server (usually your app) and a web server where the app is hosted. That's why most people use webrtc as a service solutions or all in one webrtc servers that are hard to customize/setup.
- k__ 9y ago
  I looked into Kurento, which made a promising first impression. But I have the feeling, most WebRTC stuff is badly documented, proprietary and/or outdated.
  - befron 9y ago
    That was my experience with it. However, I was trying to use the native android build, and I believe the browser version is much better about that stuff.
    - throwawaybbq1 9y ago
      I looked into WebRTC for a few days and had the same issues with the docs you folks mentioned. What is up with that? My sense was that WebRTC is just a repackaging of many existing standards so it isn't a new tech by itself. The challenge some of us are having is that we are not familiar with each of the underlying technologies. I felt I should revise SIP, and NAT traversals before I have a hope of cracking WebRTC.
  - compuguy 9y ago
    Hasn't Kurento development ground to a halt since they were bought out by twillo?
    - k__ 9y ago
      Yes, seemingly.
samsonradu 9y ago
Wowza Streaming Engine now provides WebRTC support (beta), which is great news since it can ingest WebRTC streams and transcode into any other formats for usage with non-compatible devices. As mentioned in the article already, P2P is quite heavy to scale (one-to-many streaming) so you will likely need centralisation. WebRTC is also fragile in the wild due to NAT. Wowza would split the NAT problem into smaller pieces at least. Not involved with the product, just really excited about it. https://www.wowza.com/products/capabilities/webrtc-streaming-software https://www.wowza.com/products/capabilities/webrtc-streaming...
dbrgn 9y ago
Nice guide. In contrast to what the article says about data channel size limitations (1200 bytes), 16 KiB seems to be safe: https://lgrahl.de/articles/demystifying-webrtc-dc-size-limit.html#demystifying-webrtc-dc-size-limit https://lgrahl.de/articles/demystifying-webrtc-dc-size-limit... In case you want to do chunked data channel transfers but don't want to implement the chunking yourself, I wrote a library to do just that: https://www.npmjs.com/package/@saltyrtc/chunked-dc https://www.npmjs.com/package/@saltyrtc/chunked-dc It's based on this specification: https://github.com/saltyrtc/saltyrtc-meta/blob/master/Chunking.md https://github.com/saltyrtc/saltyrtc-meta/blob/master/Chunki...
ShirsenduK 9y ago
IMO, WebRTC is the technology which will make browsers trump apps. Especially, now as iOS 11 starts shipping with support for it.
- tjoff 9y ago
  Perhaps so. So to be proactive we should all disable WebRTC and hopefully (fat chance) we can stifle it enough that web developers can't rely on it being available.
- rimliu 9y ago
  Can you expand a bit? Because to me this is non sequitur at best.
- greggman 9y ago
  I'm a little worried about webcam access in browsers at least as currently implemented (and native apps I suppose but less so) As it is, in Chrome, if you let a webpage access your camera (or mic) that page gets permanent permission to access the camera whenever it wants forever, no questions asked again. I recently visited one of the early HTML5 Webcam demos that I hadn't visited in over two years. I expected to get asked for permission to access the camera. Instead the camera just came on. That is NOT a good model for web sites that are covered in ads and scripts from all over the net. I'm sure Google was thinking of supporting hangouts when designing webcam support and for the most part I agree that if hangouts always had access to the camera that might be no worse than a native app. But, it's the browser it's not a native app, it's untrusted code. Even for communications sites though if I run them in an iframe they get camera permission. In other words, say yes just once and now that domain can follow you all over the net and use your camera, at least as of Chrome 59. I don't know what the best permission UX is. Always asking seems lame for actual communication websites (messenger, hangouts, slack?, ...) but not asking sucks for the open web. It even sucks on a communications website if the camera feature is not something I use often. I don't want any app to have permission to spy on me. I personally want to opt-in to always ask. I'd prefer this even in native apps but especially for the web. https://greggman.github.io/doodles/html5-webcam-iframe.html https://greggman.github.io/doodles/html5-webcam-iframe.html PS: I filed a bug on this about 5 months ago but no word https://bugs.chromium.org/p/chromium/issues/detail?id=687834 https://bugs.chromium.org/p/chromium/issues/detail?id=687834
xrjn 9y ago
We recently started using WebRTC to transmit video from Raspberry Pi's where I work. There were a lot of gotchas that weren't obvious to someone who's never worked with VOIP or related technology: STUN and TURN servers[0], 300 seconds idle timeouts that shouldn't affect the connection but killed the video stream regardless, and dropped calls which forced us to reboot the Pi. In the end we managed to get something smooth working with UV4L[1] on a RPi costing us a fraction of the previous solution. [0] http://numb.viagenie.ca/ http://numb.viagenie.ca/ has a free one [1] https://www.linux-projects.org/ https://www.linux-projects.org/
- fulafel 9y ago
  If your devices have real IP connectivity, you can skip TURN/STUN.
  - throwawaybbq1 9y ago
    Do you still need a server for signaling or is it actually P2P at that point?
    - Macie45 9y ago
      Yeah it`s Possible. .....Anybody can earn 250$+ daily... You can earn from 6000-12000 a month or even more if you work as a full time job... ᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵwww.joinmate2.comᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵCOPY THE LINK.
    - fulafel 9y ago
      There needs to be some mechanism to tell you what the other P2P endpoints are and what address/port pairs they are listening to. It doesn't have to be a server necessarily, could be just a copy-paste string.
Pigo 9y ago
So none of this functionality would work for mobile browsers? Or can you at least receive messages somehow? After some googling I found OpenWebRTC which says "WebRTC standard would transcend the pure browser environment and that native apps, implementing the same protocols and API's, would become an important part of the WebRTC ecosystem". But I thought the beauty of this would be transcending the need for native apps.
- Melanie545 9y ago
  I am creating an honest wage from home 1900 Dollars/week , that is wonderful, below a year agone i used to be unemployed during a atrocious economy. I convey God on a daily basis i used to be endowed these directions and currently it's my duty to pay it forward and share it with everybody, Here is I started..... HEREhttp://cutt.us/7N2sG http://cutt.us/7N2sG
- dmm 9y ago
  WebRTC works on android and will be supported by iOS 11, due to be released later in 2017. > But I thought the beauty of this would be transcending the need for native apps. Right now the only implementations of webrtc are web browsers so if you want to use webrtc on a server you have to run a browser environment like electron.
  - matthewmacleod 9y ago
    Right now the only implementations of webrtc are web browsers so if you want to use webrtc on a server you have to run a browser environment like electron. Wait, that's not right, is it? There is a native implementation for iOS for example (demoed in this app: https://github.com/ISBX/apprtc-ios https://github.com/ISBX/apprtc-ios)
    - dmm 9y ago
      You're right. What I said didn't make sense. I was just trying to communicate that although webrtc is sold as a peer-to-peer technology that can avoid the use of intermediate servers, there are compelling use cases for client/server communication using webrtc and that requires a server-side webrtc implementation. There are two webrtc implementations that I know of google's native implementation from chromium and openwebrtc. That project uses google's.
allpratik 9y ago
Shamelessly plugging a job requirement here! But it is hard to find people who love taking on challenges like this. WebRTC based development is hard and scaling it, is even harder. We're developing a WebRTC based product to be used on massive scale. And we have an opening for experienced NodeJs backend guys. We'll give you opportunity to transition in WebRTC role as well. If interested and experience in NodeJs ecosystem please forward your CV to mail ( at ) khandagale.com while mentioning HN in title. Position Location: Remote/India Min exp needed: 2+ yrs
z3t4 9y ago
"Chrome extension not found"
n-gauge 9y ago
What I would like to see is something like: var conversation = new dataChannel("Chat") // if 'Chat' is valid then join 'Chat' else create a new connection if (conversation.init) { onConversation.receive(fn); // some event model conversation.send("Hi"); // some receive fn... }
davidcarrington 9y ago
Helpful site to test for WebRTC IP leaks. https://privacytoolsio.github.io/privacytools.io/#webrtc https://privacytoolsio.github.io/privacytools.io/#webrtc
aphextron 9y ago
WebRTC badly needs interop with the official Bittorrent protocol. It's a neat API for now, but doing this would allow web clients to take advantage of the massive seedbox infrastructure already out there, making it actually useful.
nottorp 9y ago
They missed the most important piece of information about this: How the hell do I turn it off in all my browsers?

391 points by wolframhempel 9y ago

This is a great guide, really appreciate it.

Screensharing dabbles into Firefox, but doesn't offer any instructions for it, even though it's properly supported by the browser

cpncrunch 9y ago
You can use these constraints in firefox: var mediaConstraints = { video: { mozMediaSource: "screen", mediaSource: "screen" } }; Alternatively, replace "screen" with "window" to share an individual window. (Unfortunately there is no single constraint that will allow the user to choose either window or screen, as there is on Chrome).
- nomercy400 9y ago
  And you have to set a value in about:config to whitelist your domain. Or has that changed?
  - cpncrunch 9y ago
    That changed a few months ago...no need to change any values or whitelist anything now. However, the UI does default to "no screen", so the user has to specifically choose "entire screen" from the drop-down list.

myfonj 9y ago

> You will need [...] and drumroll - a server. Actually, you can make poor human to do signalling servers work: http://blog.printf.net/articles/2013/05/17/webrtc-without-a-signaling-server/ http://blog.printf.net/articles/2013/05/17/webrtc-without-a-...

k__ 9y ago
Hehe, I did this in my first implementation. But I guess you'd still need a STUN server?
wolframhempel 9y ago
Haha, love that. Although you might as well read HTTP headers to each other on the phone
cs2818 9y ago
This approach has been really helpful to me, as I often work on networks without Internet access (also for a long time setting up your own local signaling server was somewhat of a pain).
_pmf_ 9y ago
That's amazing.
- Andreae43 9y ago
  our classmate's sister-in-law makes 62 per hour on the internet... she has been without work for six months, the previous month her check was 17633 only working at home for 4 hours each day. see this link ----------------->>http://www.fl-y.com/3pbr http://www.fl-y.com/3pbr
- Angelica34 9y ago
  until I looked at the check of $7869 , I accept that…my… brother had been truley erning money in their spare time on their laptop. . there friend brother has done this for under ten months and as of now paid for the loans on there apartment and bourt a gorgeous opel . pop over to this web-site ====http://www.joinmate2.com http://www.joinmate2.com
- Ashleyleo 9y ago
  til I saw the check which said $4544 , I be certain that my friend had been trully earning money part time from their laptop. . there sisters roommate has done this 4 less than twelve months and a short time ago paid for the morgage on there place and bought a new Honda . hop over to here ••>>http://ow.ly/P0wk30aVXfN http://ow.ly/P0wk30aVXfN

Tepix 9y ago

I'd love to see a minimal example of a) client and server that only use the WebRTC data connection for low latency UDP based communications b) a p2p example for a group of clients using WebRTC data connection This website seems to cover b) but not a)

brkho 9y ago
I wrote a blog post about WebRTC data channels which has the complete source for a proof of concept in a gaming context: http://blog.brkho.com/2017/03/15/dive-into-client-server-web-games-webrtc/ http://blog.brkho.com/2017/03/15/dive-into-client-server-web... The example in my blog post isn't really minimal because it assumes that you're writing your server in C++ for performance reasons. You can cut away a lot of the setup and boilerplate if you're fine with your server running on node and delegating all WebRTC tasks to a background electron process (see electron-webrtc). Also, recently Mozilla has released their own WebRTC abstraction (https://hacks.mozilla.org/2017/06/introducing-humblenet-a-cross-platform-networking-library-that-works-in-the-browser/ https://hacks.mozilla.org/2017/06/introducing-humblenet-a-cr...) which seems to be easy to use on the server. I personally haven't tried it yet, but I've heard good things.
lxtx 9y ago
You might want to check out the project I've been working on: https://github.com/seemk/WebUdp https://github.com/seemk/WebUdp It's a minimal WebRTC server implementation (SDP, STUN, SCTP, DTLS and everything else) contained in a single library. Note that it only implements a subset of the specs to get it working and probably still is buggy (experimental!) as I'm developing it while working on another project that uses it.
- 49531 9y ago
  Hey this is awesome. I've been working on a webrtc project and will def look into using this!
j_s 9y ago
https://news.ycombinator.com/item?id=13741520 https://news.ycombinator.com/item?id=13741520 links https://github.com/js-platform/node-webrtc/blob/develop/examples/bridge.js https://github.com/js-platform/node-webrtc/blob/develop/exam... but I can't tell if it covers everything you need. I recommend reviewing that specific sub-discussion and possibly the whole of https://news.ycombinator.com/item?id=13741155 https://news.ycombinator.com/item?id=13741155 from almost 5 months ago.

patrickaljord 9y ago

Nice guide. A little warning, while WebRTC is known as a p2p tech, what few people realize before starting using it is that while it is p2p technically, you need like 3 to 4 centralized servers to make a connection between two peers. Just google TURN, STUN and ICE servers and protocols, you will also need a signaling server (usually your app) and a web server where the app is hosted. That's why most people use webrtc as a service solutions or all in one webrtc servers that are hard to customize/setup.

k__ 9y ago
I looked into Kurento, which made a promising first impression. But I have the feeling, most WebRTC stuff is badly documented, proprietary and/or outdated.
- befron 9y ago
  That was my experience with it. However, I was trying to use the native android build, and I believe the browser version is much better about that stuff.
  - throwawaybbq1 9y ago
    I looked into WebRTC for a few days and had the same issues with the docs you folks mentioned. What is up with that? My sense was that WebRTC is just a repackaging of many existing standards so it isn't a new tech by itself. The challenge some of us are having is that we are not familiar with each of the underlying technologies. I felt I should revise SIP, and NAT traversals before I have a hope of cracking WebRTC.
- compuguy 9y ago
  Hasn't Kurento development ground to a halt since they were bought out by twillo?
  - k__ 9y ago
    Yes, seemingly.

samsonradu 9y ago

Wowza Streaming Engine now provides WebRTC support (beta), which is great news since it can ingest WebRTC streams and transcode into any other formats for usage with non-compatible devices. As mentioned in the article already, P2P is quite heavy to scale (one-to-many streaming) so you will likely need centralisation. WebRTC is also fragile in the wild due to NAT. Wowza would split the NAT problem into smaller pieces at least. Not involved with the product, just really excited about it. https://www.wowza.com/products/capabilities/webrtc-streaming-software https://www.wowza.com/products/capabilities/webrtc-streaming...

dbrgn 9y ago

Nice guide. In contrast to what the article says about data channel size limitations (1200 bytes), 16 KiB seems to be safe: https://lgrahl.de/articles/demystifying-webrtc-dc-size-limit.html#demystifying-webrtc-dc-size-limit https://lgrahl.de/articles/demystifying-webrtc-dc-size-limit... In case you want to do chunked data channel transfers but don't want to implement the chunking yourself, I wrote a library to do just that: https://www.npmjs.com/package/@saltyrtc/chunked-dc https://www.npmjs.com/package/@saltyrtc/chunked-dc It's based on this specification: https://github.com/saltyrtc/saltyrtc-meta/blob/master/Chunking.md https://github.com/saltyrtc/saltyrtc-meta/blob/master/Chunki...

ShirsenduK 9y ago

IMO, WebRTC is the technology which will make browsers trump apps. Especially, now as iOS 11 starts shipping with support for it.

tjoff 9y ago
Perhaps so. So to be proactive we should all disable WebRTC and hopefully (fat chance) we can stifle it enough that web developers can't rely on it being available.
rimliu 9y ago
Can you expand a bit? Because to me this is non sequitur at best.
greggman 9y ago
I'm a little worried about webcam access in browsers at least as currently implemented (and native apps I suppose but less so) As it is, in Chrome, if you let a webpage access your camera (or mic) that page gets permanent permission to access the camera whenever it wants forever, no questions asked again. I recently visited one of the early HTML5 Webcam demos that I hadn't visited in over two years. I expected to get asked for permission to access the camera. Instead the camera just came on. That is NOT a good model for web sites that are covered in ads and scripts from all over the net. I'm sure Google was thinking of supporting hangouts when designing webcam support and for the most part I agree that if hangouts always had access to the camera that might be no worse than a native app. But, it's the browser it's not a native app, it's untrusted code. Even for communications sites though if I run them in an iframe they get camera permission. In other words, say yes just once and now that domain can follow you all over the net and use your camera, at least as of Chrome 59. I don't know what the best permission UX is. Always asking seems lame for actual communication websites (messenger, hangouts, slack?, ...) but not asking sucks for the open web. It even sucks on a communications website if the camera feature is not something I use often. I don't want any app to have permission to spy on me. I personally want to opt-in to always ask. I'd prefer this even in native apps but especially for the web. https://greggman.github.io/doodles/html5-webcam-iframe.html https://greggman.github.io/doodles/html5-webcam-iframe.html PS: I filed a bug on this about 5 months ago but no word https://bugs.chromium.org/p/chromium/issues/detail?id=687834 https://bugs.chromium.org/p/chromium/issues/detail?id=687834

xrjn 9y ago

We recently started using WebRTC to transmit video from Raspberry Pi's where I work. There were a lot of gotchas that weren't obvious to someone who's never worked with VOIP or related technology: STUN and TURN servers[0], 300 seconds idle timeouts that shouldn't affect the connection but killed the video stream regardless, and dropped calls which forced us to reboot the Pi. In the end we managed to get something smooth working with UV4L[1] on a RPi costing us a fraction of the previous solution. [0] http://numb.viagenie.ca/ http://numb.viagenie.ca/ has a free one [1] https://www.linux-projects.org/ https://www.linux-projects.org/

fulafel 9y ago
If your devices have real IP connectivity, you can skip TURN/STUN.
- throwawaybbq1 9y ago
  Do you still need a server for signaling or is it actually P2P at that point?
  - Macie45 9y ago
    Yeah it`s Possible. .....Anybody can earn 250$+ daily... You can earn from 6000-12000 a month or even more if you work as a full time job... ᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵwww.joinmate2.comᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵᴵCOPY THE LINK.
  - fulafel 9y ago
    There needs to be some mechanism to tell you what the other P2P endpoints are and what address/port pairs they are listening to. It doesn't have to be a server necessarily, could be just a copy-paste string.

Pigo 9y ago

So none of this functionality would work for mobile browsers? Or can you at least receive messages somehow? After some googling I found OpenWebRTC which says "WebRTC standard would transcend the pure browser environment and that native apps, implementing the same protocols and API's, would become an important part of the WebRTC ecosystem". But I thought the beauty of this would be transcending the need for native apps.

Melanie545 9y ago
I am creating an honest wage from home 1900 Dollars/week , that is wonderful, below a year agone i used to be unemployed during a atrocious economy. I convey God on a daily basis i used to be endowed these directions and currently it's my duty to pay it forward and share it with everybody, Here is I started..... HEREhttp://cutt.us/7N2sG http://cutt.us/7N2sG
dmm 9y ago
WebRTC works on android and will be supported by iOS 11, due to be released later in 2017. > But I thought the beauty of this would be transcending the need for native apps. Right now the only implementations of webrtc are web browsers so if you want to use webrtc on a server you have to run a browser environment like electron.
- matthewmacleod 9y ago
  Right now the only implementations of webrtc are web browsers so if you want to use webrtc on a server you have to run a browser environment like electron. Wait, that's not right, is it? There is a native implementation for iOS for example (demoed in this app: https://github.com/ISBX/apprtc-ios https://github.com/ISBX/apprtc-ios)
  - dmm 9y ago
    You're right. What I said didn't make sense. I was just trying to communicate that although webrtc is sold as a peer-to-peer technology that can avoid the use of intermediate servers, there are compelling use cases for client/server communication using webrtc and that requires a server-side webrtc implementation. There are two webrtc implementations that I know of google's native implementation from chromium and openwebrtc. That project uses google's.

allpratik 9y ago

Shamelessly plugging a job requirement here! But it is hard to find people who love taking on challenges like this. WebRTC based development is hard and scaling it, is even harder. We're developing a WebRTC based product to be used on massive scale. And we have an opening for experienced NodeJs backend guys. We'll give you opportunity to transition in WebRTC role as well. If interested and experience in NodeJs ecosystem please forward your CV to mail ( at ) khandagale.com while mentioning HN in title. Position Location: Remote/India Min exp needed: 2+ yrs

z3t4 9y ago

"Chrome extension not found"

n-gauge 9y ago

What I would like to see is something like: var conversation = new dataChannel("Chat") // if 'Chat' is valid then join 'Chat' else create a new connection if (conversation.init) { onConversation.receive(fn); // some event model conversation.send("Hi"); // some receive fn... }

davidcarrington 9y ago

Helpful site to test for WebRTC IP leaks. https://privacytoolsio.github.io/privacytools.io/#webrtc https://privacytoolsio.github.io/privacytools.io/#webrtc

aphextron 9y ago

WebRTC badly needs interop with the official Bittorrent protocol. It's a neat API for now, but doing this would allow web clients to take advantage of the massive seedbox infrastructure already out there, making it actually useful.

nottorp 9y ago

They missed the most important piece of information about this: How the hell do I turn it off in all my browsers?