* Distributed by default - Designed to allow running different workloads and scaling them out as you need
* Flutter and JS SDK - Ready to be used on Web, Android and iOS!
* Designed to be modified - Modify the UI/Backend so you can have custom experiences for your use cases. As long as you satisfy public APIs any piece can be swapped.
* Easy to deploy - docker-compose with LetsEncrypt support. Spin up a conference server with on command
* Performant - You can run multi person conference calls on AWS free tier instances
* A joy to develop - Pure Go means quick builds, and a code base that anyone can contribute too!
* Community owned - The only thing driving the project is the contributors and users
We also plan on adding lots more, with some of the following in our road-map already.  If you are interested in learning more about some of this stuff, this is a great chance! It is really rewarding seeing all the innovative things being built.
* RTMP Ingestion
* SIP Support
* Server Side Processing/OpenCV
* Record calls
We would also love to have you! If you are interested in working on this project you should join our Slack
I think it is a self-hosted video conferencing solution, which sounds awesome, but I'm not certain of that. I assume "RTC System" is not a real-time clock. I've heard of Go, and Flutter sounds like some sort of Web UI system.
Can anyone explain this a little more simply, please?
I will work on making the README more friendly! If anyone else is interested I would love help, working in this space has made me biased so I tend to write thing for myself.
And, that's a good point. The curse of knowledge is real :-)
It looks like a lot of progress has been made since the last time I visited the repo.
I suppose it's time for me to learn Go.
I think it is super important to have multiple implementations of important protocols (like WebRTC, DTLS and SCTP). It brings more resiliency, and it helps people learn them. It seems like in tech a lot of things get re-invented just because we don't do a good job of teaching the next generation...
We would love to have you join the community ! If you have any questions/thoughts while learning Go and Pion I will be there to answer them.
It seems to bind to a large number of ports (including a port 80 redirector, which isn't really helpful on a host that's likely to be serving other stuff), and I can only assume there's some hidden firewall dependency that I've missed.
Such as shame, as it shows great promise.
I had a quick look only so apologies if I missed it, but are there any build/deploy instructions that do not require Docker?
It's definitely a tricky problem though, which is why I figured a more customizable solution would be better.
I am going to work on writing an Apache Bench for WebRTC this year though. It is really hard to load test/bench this stuff because the tooling just doesn't exist. A lot of people roll out WebRTC, but then go down under real world load.
in summary, if you have first class clients you can "host" a million person session in a raspberypi. if you have two bad clients, you better have tons of cpu and bandwidth!