31–40 of 107 posts
If this is backed by Twilio cloud webRTC API, I believe that does not support more that 50 people at a time watching the video
The bottom mentions that peer-to-peer room pricing is even lower, $0.18/hr for a two-person meeting, but I'm not sure when that's used.
These are open source clients for a proprietary backend, which are no doubt still useful in a number of circumstances. If you are comfortable with a more proprietary stack, then Google Hangouts / Zoom / others are likely to provide a better supported user experience. If you would prefer a more libre end-to-end experience then Jitsi Meet may be an attractive alternative.
Zoom is owned indirectly by the Chinese government, not sure what that means to your company but FYI.
Earlier quoted context omitted.
You quite explicitly don't need to audit the backend to verify something is end to end encrypted. I can be confident nobody is snooping on my TLS communications without needing to audit every router along the way, this is in some ways the entire point.
The point of e2e encryption is that the server can't decrypt it.
Earlier quoted context omitted.
Is it trivial to write a backend that will replace the functionality in Twilio's backend?
It may not be entirely trivial but if enough people are willing to contribute it could be trivial on an individual basis. I'd be interested in giving it a go. If anyone else is, just leave a comment on this issue. https://github.com/ethanwillis/oss-twilio-video-backend/issu...
Earlier quoted context omitted.
That doesn't sound like him :) Do you have a reference/quote for that, out of interest? In the past it seems like he's been skeptical[0] of providing user data to third-party services. [0] - https://www.theguardian.com/technology/2008/sep/29/cloud.com...
This was from a private email exchange, but you can look at how he's soliciting a FOSS Google Docs client as evidence that he'd be fine with a FOSS interface to a proprietary service. Additionally, https://www.gnu.org/philosophy/javascript-trap.html makes no mention of proprietary backends being harmful to user freedom, only obfuscated (unauditable) frontend code.
It'd be great to learn more about that call for a FOSS Google Docs client if you can share a hyperlink.
I'm seeing discussion below about fully open-source solutions (Jitsi Meet) vs. fully proprietary solutions (Zoom). What's interesting about using Twilio is that it is a programmable solution.
Case in point: I am building a webpage where people can log-in to a virtual office, so that people working from home don't feel so lonely. I have certain requirements, such as:
- All audio is muted
- Participants are arranged in a grid
- Room is persistent (no need for an "owner")
Now, Twilio isn't the only Video platform on the market (see TokBox, etc), but I think comparing this to Jitsi/Zoom/Hangouts is like comparing apples to oranges.
Earlier quoted context omitted.
It may not be entirely trivial but if enough people are willing to contribute it could be trivial on an individual basis. I'd be interested in giving it a go. If anyone else is, just leave a comment on this issue. https://github.com/ethanwillis/oss-twilio-video-backend/issu...
Right, but you're talking about starting an open source project whose complexity is similar to that of Jitsi's backend. It may be hard to attract contributors until there's a proof of concept.
However if people do want to contribute early on I'd welcome that :)
Disclaimer: I used to work at Twilio I'm seeing discussion below about fully open-source solutions (Jitsi Meet) vs. fully proprietary solutions (Zoom). What's interesting about using Twilio is that it is a programmable solution. Case in point: I am building a webpage where people can log-in to a virtual office, so that people working from home don't feel so lonely. I have certain requirements, such as: - All audio is…
Disclaimer: I used to work at Twilio I'm seeing discussion below about fully open-source solutions (Jitsi Meet) vs. fully proprietary solutions (Zoom). What's interesting about using Twilio is that it is a programmable solution. Case in point: I am building a webpage where people can log-in to a virtual office, so that people working from home don't feel so lonely. I have certain requirements, such as: - All audio is…
Where I think it does play in is that while Zoom is probably making a lot of sales right now, they are probably starting to regret their start-up friendly pricing model now that they have to fund large engineering efforts to keep up with demand. I imagine Zoom prices will go up while Twilio APIs will stay fairly consistent. There may be some cool start-ups that get built on top of this as well.