webrtc

I think SCTP was a very good choice. Writing a SCTP implementation for Pion WebRTC[0] was really enjoyable. The SCTP RFC is well written and easily available [1]. Once you learn all the chunk types things start to fall into place. SCTP is also battle tested and we know what flaws it has. I am pessimistic about alternatives * New protocols/changes are spread across multiple drafts, and they are abandoned once they land in browsers. Most of the time these changes are already going to happen and these drafts are just a way to notify the general public it is happening. So it ends up being 'the implementation is the spec', and things are brittle. SCTP doesn't break like that. * WebRTC is still very difficult to use. For large dev teams/corporations it is a solved problem, but I really wish there was more excitement/emphasis around lowering the

Demonstration of connecting a Go process with your browser, and no backend is required! If you are building a PWA you could have two browsers connect to each other in the same LAN, with no internet access required to bootstrap the connection. Just choose two unique IDs and then they could find each other. I would love to build a chat application that maybe auto-connected people if they were inside the same network. My motivation for building this is showing what WebRTC can be used for, and maybe pushing the standards bodies to support this behavior more. I also work on https://github.com/pion/webrtc a full Go implementation of WebRTC and just enjoy the space. Would love to hear what people think, someone started a twitter thread about it https://twitter.com/_developit/status/1203352686869004289. Seems like a super cool idea and I think co

Hey Keith, Amazing work, I am really impressed with what you are doing. I have never found any good reading in this area beside your work, the only thing I have seen is GStreamer's rtpjitterbuffer and libwebrtc. I haven't really felt confident in what I have learned from either though. Have you thought about testing/comparing against other WebRTC implementations? It makes me a little sad to see WebRTC get a bad name just because one implementation has issues. WebRTC is a huge opportunity to get companies to invest in one thing, instead of reinventing the wheel and locking people in. Do you think things could be improved and eventually match Salsify? Somewhat unrelated but I am working on Pion WebRTC[0]. By design it is not coupled tightly with the encoder/decoder (but I want to give feedback to the user so it could influence it if they wa

Super cool project I just saw on Reddit! I work on https://github.com/pion/webrtc and was excited to see another project using the library. If you are new to WebRTC this is super cool because you could easily share your desktop with no central server required. So could easily be used for LANs or building your own broadcast server over the internet.

I have only been doing Pion WebRTC(https://github.com/pion/webrtc) for a year, but the hardest ones for me have been * Relationships tied to the project It sort of burned me out when the first contributors moved on. I have always been on the other side though, interests change or you change jobs. * Every user issue is urgent. It is hard figuring out what the most important thing to work on is. If a user takes time to file an issue it is causing them issues. I just have been on the other side and it doesn't feel great to be ignored. * Community members with different communication styles People aren't so much assholes, but just communicate differently. It is really hard to mediate, no one is at fault but I just hate seeing people leave/get burned out from it.

If you are new to WebRTC it is a really amazing technology, and lots of powerful things can be built with it. It isn't just a technology for conferencing, you can build powerful P2P software that works on all platforms (including your browser!) You can see it in use in places like IPFS[0] so come check out the examples[1] and build something cool. We also would love to chat! You can find us on Slack[2], while this channel was started for Pion there is a lot of interesting general WebRTC conversation going on. ---- I am excited to announce that v2.0.* has officially landed and stabilized! Multiple large production users have migrated to it and we fixed all the bugs we found along the way. This was a really big release, you can see the full release notes[3] are some exciting parts though. * Unified Plan and Plan-B support * QUIC Support * W

Transfer is done via DTLS, a protocol on top of UDP, so we have to deal with packet loss and retransmission, which itself is controlled by SCTP. gfile uses pion/sctp[0] (via pion/webrtc[1]), and there has been some work going on to improve performances. :) The performances used to be far worse, but with the recent improvements on pion/sctp, I felt gfile had become fast enough to be useful to some people. [0]: https://github.com/pion/sctp [1]: https://github.com/pion/webrtc

This is super exciting, so many cool things happening here. I haven't had a chance to grok it fully yet but someone added WASM support to pion recently [0] you will able to just write your code once in Go and should work in both places! https://github.com/pions/webrtc/blob/master/examples/README....

Yup, lots of telephony-inspired RFCs in there. If you're not already, I suggest referencing [0] as you develop, it's a great project that is also really easy to read what's happening underneath. 0 - https://github.com/pions/webrtc