Given a choice between Cost and Stable, if you have to prioritize one, which is It?
Then we’re going to compare the others against each other. Then we’re going to add in security of the stream. Then logging. Then privacy. Then security of the auth. Then suggest federation. Then interoperability with other media like POTS. Then anonymity. Then spam resistance. Then identity/trust assurance. Then your OS preference, server and client. Then onPrem (or private cloud) vs public cloud. Then apps vs appliances vs containers. Then C vs Java vs Rust vs perl.
Define “good”?
There are a thousand public instances you can demo or just use.
Stable, easy to use, low to little cost.
Now rank those.
Given a choice between Cost and Stable, if you have to prioritize one, which is It?
Then we’re going to compare the others against each other. Then we’re going to add in security of the stream. Then logging. Then privacy. Then security of the auth. Then suggest federation. Then interoperability with other media like POTS. Then anonymity. Then spam resistance. Then identity/trust assurance. Then your OS preference, server and client. Then onPrem (or private cloud) vs public cloud. Then apps vs appliances vs containers. Then C vs Java vs Rust vs perl.
Get cracking. “Good” has so many facets.
I mean in terms of use it’s virtually identical to other webconferencing apps, minus some features.