Currently, loop client (in firefox and in the webapp) relies on opentok. The code should be made pluggable so it allows the client to use a different implementation than tokbox; This is specifically important as the code tokbox provides isn't open source, and relies heavily on their infrastructure. WebRTC is a technology that allows to do p2p communications, that would be too bad to let the signaling part of firefox loop be provided *only* by a specific partner.
We're not going to be able to do anything in this area in any known timescale
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.