- To schedule and invite to a call
- Securely protect a call and only invite certain people
- Be sure that the call is end not listened in on
As of the latest update, these are no longer missing features… You can create a call by referencing the id of the call topic, for example: https://now.edgeryders.eu/call/12876
This will only allow a user to join the call at the scheduled time, and only for the users listed in the RSVP. You can also limit access by discourse groups.
For the other two points, muting and kicking out participants is very easy to implement with the Daily.co API. I haven’t been able to test it with 20+ people but from my experience with it, the quality and latency is as good or better than any other service I have tested.
This isn’t to say another solution wouldn’t also work - but I would consider carefully where our resources should be spent if we have something working already…
I think the shortcomings you listed are less related to the API we are using, as they are to UI features that can be implemented… but there isn’t much sense in implementing them if we’re not sure which solution to go with.
From what I read about Jitsi, the benefits would be that it is open source, which I understand aligns better with the core values (but then again we are still using services like YouTube and Mailchimp, which are proprietary…). But the downside would mean running an extra server (just talked to @matthias about how we would like to avoid this), maintenance and associated costs - for something that does one thing.
The admin interface would also be an extra level of UI, arbitrarily disconnected from our platform - while the current system relies quite nicely on topics on the platform - that are open and editable.
This isn’t merely to play devil’s advocate (or push us for using daily.co - of which I own no stock ), but just to point out some things that should be considered before jumping into another pond…
/cc @nadia @hugi