Yes p2p, so to support higher numbers of people you'd need either a server somewhere doing compositing or selective forwarding (etc). I think a smart front-end

Yes p2p, so to support higher numbers of people you'd need either a server somewhere doing compositing or selective forwarding (etc). I think a smart front-end client could do selective forwarding but would be tricky to get right (e.g. to consistently detect and forward the speaker). EDIT: I meant to include, WebRTC itself does not prohibit such things, so the point was for small stuff it works w/ minimal setup, dumb client, and for bigger stuff it would still work, but would need more robust supporting code.