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.
Comment on Does anyone have experience with Mumble?
splendoruranium@infosec.pub 3 weeks ago
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 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 persistance beyond the room setup and only limited backend options. Keep that in mind.
waddle_dee@lemmy.world 3 weeks ago
splendoruranium@infosec.pub 5 days ago
I don’t see why not. Again, the resource footprint is so tiny that you can just throw in Mumble anywhere. You can make it tinier still if you limit sending pictures via that chat and allocate a maximum bandwidth via the config.
themachine@lemmy.world 3 weeks ago
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.
waddle_dee@lemmy.world 3 weeks ago
Awesome, didn’t know if there was any sort of risk associated. Thanks!
themachine@lemmy.world 3 weeks ago
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.
ruuster13@lemmy.zip 3 weeks ago
If pi zero, you’re serving 12 users low latency over wifi? Does it route the actual audio?
splendoruranium@infosec.pub 5 days ago
If pi zero, you’re serving 12 users low latency over wifi? Does it route the actual audio?
Yes, it’s sufficient. I wouldn’t advise it due to the extra overhead of wireless packet loss, but it’s absolutely technically possible. Don’t overestimate how little bandwidth voice chat really needs. It’s like 10-50kB/s per person and you’re unlikely to ever have more than 2 or 3 people talking at a time.
nfreak@lemmy.ml 3 weeks ago
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