132
Why is self-hosted voice chat so hard?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Feb 2026
132 points (97.8% liked)
Selfhosted
62293 readers
307 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
Simple 1:1 audio stream is easy.
Groups, screen sharing, noise canceling, NAT traversal, mobile apps, and all those extra features people have come to expect are hard.
Exactly!
people act entitled as if all that you mention was trivial and that somehow FOSS devs "owe" people, but we only see those big corpos make it happen because... well, they're big corpos, burning VC money on makint it happen and making it happen in a controlled jail.
I have honestly not seen anyone acting like they are "owed" these things by FOSS developers. We just want them.
I have seen lots of people. Mostly not here, but that's because we here know better (I'd hope). Runs along with usual complaints such that they can't move from a platform with 9trillion captive users to a new budding platform, conveniently forgetting that when they began Shitter and stuff also had like 0 users yet people did move.
As for "why is it hard to self-host", it is only NAT traversal.
TURN, STUN, ICE, etc. are not fun to debug. Not sure if anyone still bothers fiddling with TOS/DSCP on their router. You can build a voice server that just exposes a TCP port, but... latency. And corporate firewalls love to randomly block some UDP port ranges but not others.
Mumble will do all of that except screen sharing. Only the server has to deal with NAT.
The one point that has basically been solved is NAT traversal. Thanks to Wire guard, Tailscale and the like. The relevant parts are open source and can be used basically as a library.
Groups: just simple Chanels are fine, password lock them if you want.
Screen sharing: one at a time should be fine. Self hoster can configure max bit rates.
Mobile apps: building your app to be multiplatform is a lot easier than it was a decade ago.