Administered by:
@makeworld Messaging is very different from real time communications.
WebRTC leaks are notoriously difficult to contain. It would have to be a hardened implementation that takes care of all the negotiation via a secure channel, and then routes packets around as to not disclose the origin and destination of a given communication.
You may be already familiar with WebRTC I assume, but hardening it for privacy is orders of magnitude harder than doing the same for a messaging service.
@makeworld I mean, if you want to keep a reasonable video frame rate/kbps audio rate that is acceptable for synchronous human communication.