3 ms·

WebRTC requires some sort of external communication channel to exchange information about how to set up the connection. (Often referred to as signaling messages

WebRTC requires some sort of external communication channel to exchange information about how to set up the connection. (Often referred to as signaling messages). Disclaimer: Google employee, work on the WebRTC team.

marknadal 8y ago
Grandparent: After getting frustrated with all the other WebRTC libraries over the last 4 years, I finally wrote our own ( https://github.com/amark/gun/blob/master/lib/webrtc.js https://github.com/amark/gun/blob/master/lib/webrtc.js ) which is capable of using a set of decentralized DHT relay-peers in GUN for signaling - and once peers are already on WebRTC, they can signal (daisy-chain "DAM" as we call it) to other WebRTC peers via WebRTC! Meaning, you don't/won't have to run any servers!!! Ping us on our chatroom if you want the list of DHT peers. Parent: Chuck! Sounds like you'd be a very useful person to know. Me, Feross, etc., plenty others have been requesting additional API/protocol access over the last 4 years (some of which FireFox is adding in libdweb extension!). Any chance we could connect and chat? Ping me at mark@gun.eco ?
- anderspitman 8y ago
  Would it be a problem to keep a list of DHT peers in the git repo?
  - marknadal 8y ago
    Good idea. I need to get approval they are OK with their peers being publicly listed (easy DDoS potential, we don't have code yet to [but working on it] mitigate it). I'll start one with just mine, and then others can PR to opt-in. You want to join?
    - anderspitman 8y ago
      Awesome, thanks. I'm not actually using WebRTC (or GUN) yet, but I hope to for a project relatively soon and the possibility of not requiring a STUN/ICE server is very enticing to me.
- Orphis 8y ago
  If you need to request more APIs, you should try to talk about your usecase to the WebRTC working group using the users mailing list ( https://groups.google.com/forum/#!forum/discuss-webrtc https://groups.google.com/forum/#!forum/discuss-webrtc ). Depending on the question, you may also ask on the spec Github project ( https://github.com/w3c/webrtc-pc https://github.com/w3c/webrtc-pc ). Source: Google employee, in the WebRTC WG.

marknadal 8y ago

Grandparent: After getting frustrated with all the other WebRTC libraries over the last 4 years, I finally wrote our own ( https://github.com/amark/gun/blob/master/lib/webrtc.js https://github.com/amark/gun/blob/master/lib/webrtc.js ) which is capable of using a set of decentralized DHT relay-peers in GUN for signaling - and once peers are already on WebRTC, they can signal (daisy-chain "DAM" as we call it) to other WebRTC peers via WebRTC! Meaning, you don't/won't have to run any servers!!! Ping us on our chatroom if you want the list of DHT peers. Parent: Chuck! Sounds like you'd be a very useful person to know. Me, Feross, etc., plenty others have been requesting additional API/protocol access over the last 4 years (some of which FireFox is adding in libdweb extension!). Any chance we could connect and chat? Ping me at mark@gun.eco ?

anderspitman 8y ago
Would it be a problem to keep a list of DHT peers in the git repo?
- marknadal 8y ago
  Good idea. I need to get approval they are OK with their peers being publicly listed (easy DDoS potential, we don't have code yet to [but working on it] mitigate it). I'll start one with just mine, and then others can PR to opt-in. You want to join?
  - anderspitman 8y ago
    Awesome, thanks. I'm not actually using WebRTC (or GUN) yet, but I hope to for a project relatively soon and the possibility of not requiring a STUN/ICE server is very enticing to me.
Orphis 8y ago
If you need to request more APIs, you should try to talk about your usecase to the WebRTC working group using the users mailing list ( https://groups.google.com/forum/#!forum/discuss-webrtc https://groups.google.com/forum/#!forum/discuss-webrtc ). Depending on the question, you may also ask on the spec Github project ( https://github.com/w3c/webrtc-pc https://github.com/w3c/webrtc-pc ). Source: Google employee, in the WebRTC WG.