So, I’ve been having issues with voice chat on Discord and I’m looking for alternatives. In my search, I came across Mumble, here. Does anyone here have experience, or information regarding Mumble, or a better alternative to Discord with better latency? Is it relatively easy to set up? Is it safe? Any advice and help is greatly appreciated.
Been running a server for my friends for over a decade now. Can recommend. It’s just one apt-get to set up, runs on a Pi Zero for a dozen people, has clients available for pretty much any platform and doesn’t really require any maintenance. Latency will depend on the routing between you and your friends’ ISPs, of course, but the whole purpose of the software itself was to provide a low-latency voicechat server for gaming.
But: That’s it. You don’t get anything else. It’s a barebones voice chat server. You can set up rooms and have basic text-functionality, but you don’t get any fancy user management, no full-fledged chatrooms, no persistence beyond the room setup and only limited backend options. Keep that in mind.
I haven’t used Mumble since like 2010, looks like it’s still the exact same tool as it ever was, and that’s honestly all it really needs to be. Love to see it
Would it be something that I could add to my home server? I have a setup for Nextcloud, apache, Grocy, Jellyfin, etc. So, I didn’t know if I could just throw Mumble on there. In addition, I greatly appreciate that it’s barebones! I don’t want, or need, any of the extraneous stuff Discord has. I just want to voice chat, and text like the old AIM days.
The short answer to “can you add it to your home server” is yes. It’s not like there is some cap beyond your own system resources that prevents you from running multiple services.
Awesome, didn’t know if there was any sort of risk associated. Thanks!
Well there can be some “risk” depending on how you’re going about this. I’m assuming you will be wanting people outside of your home network to be able to each your server. To do so you’ll either have to open a port in your LAN firewall and expose your server on said port to the internet, or have all users who will be using this on a VPN you create.
The former being “more risky” but quantifying that risk is difficult. Ive done this in the past and don’t personally see it as a big deal. My current mumble server does not live on my LAN but I will be pulling my server out of a local data center in the nearish future and running it out of my home once more at which point a number of publicly accessible services will be hosted from my LAN.
Yeah, my ports are open for other uses on my server, so this isn’t an issue. But I have followed the advice of a cyber security friend who helped me fortify my server against any attacks. It was fun to find a note on my root of my server with instructions lol
If pi zero, you’re serving 12 users low latency over wifi? Does it route the actual audio?