| > After reading it, I'm still not entirely sure what's being done.
> Is it live streaming or is it the transport? tonari is the entire stack, similar in "feature scope" to WebRTC but with different goals and target environments. > Are they doing video encoding (the audio encoding seems to be done by that webrtc-audio thing)? Yep, this includes video encoding and transport. We don't use the WebRTC audio library for encoding or transport, just for echo cancellation and other helpful acoustic processing. > Have they chosen a progressive encoding format that compresses frames and pumps them out to the wire as soon as they're done? Yep, basically, if by that you mean we don't use B-frames or other codec features that would require buffering multiple video frames before receiving a compressed stream, so we're able to send out encoded frames as they arrive. > Is TCP or UDP involved or a new Layer 3 protocol entirely? We encapsulate our protocol in UDP since we operate on normal internet - a new protocol is out of the question without a huge lobbying force and 15 years of patience on your side. > Have I just missed all of those parts or were they really missing amid all the Rust celebration? We intentionally didn't get into the protocol details because we are saving that for a dedicated post (and code to back it up). |
Looking forward to the technical post. If you're planning on releasing all of this royalty-free and opensource, you'd be quite a boon to the free and open internet. Getting this picked up by the likes of Mozilla and getting it into a browser would be amazing.