The audio quality is great and the latency is marvelous but I can't get normies to use it with the tedious setup wizard, poor feedback cancelling from that one person who joins with the laptop speakers and mic, and the labyrinthine security model.
Why is Discord not a good choice in your opinion?
You can, but it will be painful with captcha and email submit links for your new IPs.
Please let me know if that's not the case.
On mumble however, I start the client and it just works. Also, it instantly reconnects should the connection break.
Unless Google is employing hackers to secretly integrate reCaptcha into other apps, it is coming from Discord no matter who creates the captchas
Can take a bit of time, but needs to be non-clunky.
Discord having the slack-like features, video streaming and social networking integrated in a nice UI makes it a better all purpose consummer product unfortunately.
Is this because the server didn't have a certificate from a trusted CA? In which case the fix is that Mumble could integrate ACME to get certificates from Let's Encrypt or whoever
Or is the situation that Mumble doesn't integrate the WebPKI and so it expects the user to make trust decisions for each certificate, which is pretty hostile ?
> That is an issue of general technical illiteracy
I guess that's kind of true, but I'm not sure I should need to understand the correct range of manifold pressure for the engine in a motor vehicle to operate it, for example. "Just do what is obviously the correct thing" seems reasonable in both cases.
In my experience, a lot of people who set up a Mumble instance don't have an actual domain name, so they can't get a CA certificate, only self-signed. Most people do set up at least a dynamic DNS of some sort. But as long as you're doing that, you might as well pay the extra $10/year to get a domain, in my opinion.
Most dynamic DNS providers got a default shared domain name added to the Public Suffice List e.g. dyndns.example might be on the PSL and then you can have your server be named etskinner.dyndns.example when you call their dynamic DNS service.
In this case Let's Encrypt is quite happy to give you a certificate for etskinner.dyndns.example since you control it. Unlike a web server, the Mumble server can't trivially bake the elements needed for this into its functionality, but it shouldn't have a hard time in the two easy cases:
1. There is no web server for this DNS name, spin up a temporary web server, answer Let's Encrypt queries until they give you a certificate, then spin it back down
2. This machine is the web server, so, have the user tell us how to pass http-01 challenges on that existing web server.
That doesn't cover every corner case, and it is one more notch on your "Duplicate certificate count" rate limit if you do have an HTTPS web site on the same name from Let's Encrypt, but I'd guess 95% of users who have a working Murmur and either a Dynamic DNS setup or their own "proper" DNS setup would get a working system and a further fraction would have some trivial problem they'd fix and after that it would Just Work™.
I understand that connecting to hundreds of servers wasn't a thing in 2015 but it is just so high friction to talk to people about video games.
Well... no. The way one configures users and permissions in Mumble clearly didn't pass the mom test.
I have similar qualms with how users identify. "What? are you telling me that there are these weird files that are called <certificates> and that if I want to move between my PC, laptop, or phone, I need to hunt for this file and copy it into all my devices?" (obviously at this point people started logging in as "Joe2", "Joe3", etc. in my server)
People with a speakers setup sound awful on all software. Some kind of headphones or earbuds cost less than 10 quid.
The feedback cancelling wasn't the problem. It's a feature that should scarcely even exist.
The only time it's ever really good is when there is some sort of interactive one to many setup. A hands on demo from a lecturer where for some reason they can't wear some wireless buds.
I haven’t used it in the past year, but if I were to guess I’d say it’s in the tens of milliseconds, definitely not higher.
I use Steam voice chat to talk to my brother and I find it by far the best one. Low latency and no filter BS. I don't think it is P2P though.
I and my friends used Ventrilo earlier and the level of QoS you get from hosting on a low load computer with like 4ms ping to each node is insane compared to modern alternatives ...
For a two way call Ventrilo is essentially P2P.
I used mumble for a few years to bridge a VHF radio between an airport and a remote site via the internet. The tricky bit was getting the push-to-talk on the radio to work, which required some circuitry and some source code tweaks...