Hacker News new | ask | show | jobs
by SkiFire13 135 days ago
> I recently set up a Mumble server on my home server

That makes you an even smaller minority unfortunately. Most people are not going to set up a home server.

2 comments

It's semantics, really. Run the server executable on any computer in your house. Done. If you don't leave your computer on 24/7, the Mumble server isn't up 24/7. Oh well. If you use it to talk to friends, you'll presumably have your computer on when you want to use it yourself anyway.
> If you use it to talk to friends, you'll presumably have your computer on when you want to use it yourself anyway.

I tried this in the past but it didn't work. Now if your friends want to play you need to start the server for them. What if you're not at home? You basically end up making your pc a 24/7 server. Or you need to coordinate so that someone else runs the server in those cases, but that ends up creating more confusion. And let's not start talking about port forwarding issues...

All these issues are solvable, but they add so much friction when all you want to do is play with some friends.

I ran it on a Raspberry Pi (I think first or second gen) for a few years.

It requires next to no CPU time, since the server is effectively just a packet relay.

Mumble servers used to be just a few dollars a year (haven't looked in a long time). But even that is enough friction to prevent adoption. Plus it doesn't support any of the non-voice features.