People sacrifice a good bit of everything else, just to get a better UX, and the more developers realize this, the more potential their projects have to succeed. But if someone wants to make FOSS successful, they better focus on the user experience.
Mumble echo software#
I can see FOSS software outperform Discord, if you pick an aspect, like "low latency audio". With a buttery smooth transition to both. And you have several ways to "upgrade", you can register your handle, download and use the desktop app. You click on an invite link, it only asks you a handle, and bam, you land on the server, ready to go. The other thing is that joining is like zero effort. For one, Discord must have a serious backend and constant support to back this all up. Surely it was a bit of time to get the hang of their UX, but I can't seriously see _any_ FOSS software to do audio, video, screen sharing, IM with groups and users, all packed into a nice consistent package. Discord is featureful and each feature is only a couple of clicks away, and every nitty-gritty is nicely abstracted away under the UI. I don't know how the commenters below you miss your point consistently. 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™.
Mumble echo how to#
This machine is the web server, so, have the user tell us how to pass http-01 challenges on that existing web server. 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Ģ. 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:ġ. In this case Let's Encrypt is quite happy to give you a certificate for since you control it.
dyndns.example might be on the PSL and then you can have your server be named when you call their dynamic DNS service.
Most dynamic DNS providers got a default shared domain name added to the Public Suffice List e.g. Most people do set up at least a dynamic DNS of some sort.
0 kommentar(er)
