Design proposal: optional per-player audio/video chat during a match

[rykerwilliams]

Following up with a second design pass — this one on optional audio/video chat between the two (or more) players in a match. To be clear about scope: this is players opting in to talk to each other during their own game, not a spectator broadcast/commentary feature (that's a separate area I also looked at).

Findings, briefly:

• The existing P2P transport is already genuine browser-to-browser WebRTC via PeerJS, with an RTCDataChannel carrying game state over a Peer connection each side already holds. Adding media is a small extension — peer.call(peerId, stream) reuses the same Peer/signaling registration, not a new stack.
• STUN/TURN is already solved and paid for: the existing Cloudflare Worker that mints short-lived TURN credentials for the game-state transport works as-is for media too.
• Recommended shape: default-off, independent per-player outbound opt-in (each player only ever enables their own mic/camera), a one-time per-match inbound accept, and always-available mute/stop — and private (code/password-shared) games only at first, since there's no moderation tooling for public matchmaking today.
• Zero engine involvement required — purely client/transport, which keeps it consistent with the project's "engine owns game logic, frontend is a display layer" split.

Full write-up: rykerwilliams#2 (again, a discussion artifact against a mirror of main, not meant to merge as-is).

Genuinely unsure whether this is something you'd want upstream at all — the privacy and moderation surface of live faces/voices is a real, different category of concern than the game-state feature it'd sit next to, and that's exactly the kind of call I wanted your read on before anyone builds it.