this post was submitted on 13 Feb 2026
128 points (98.5% liked)

Selfhosted

56397 readers
1803 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

All this talk about Discord replacements plus my own experience attempting to host a Synapse has got me wondering why it seems so hard to implement voice chat.

Stupid idea: back in 2022 I got an Asterisk server working on a raspberry pi over AREDN without too much trouble. What's stopping people from just using a PBX like that for voice chat?

you are viewing a single comment's thread
view the rest of the comments
[–] frongt@lemmy.zip 102 points 2 days ago (5 children)

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.

[–] lambalicious@lemmy.sdf.org 27 points 2 days ago (1 children)

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.

[–] iamthetot@piefed.ca 14 points 1 day ago (1 children)

I have honestly not seen anyone acting like they are "owed" these things by FOSS developers. We just want them.

[–] lambalicious@lemmy.sdf.org 5 points 1 day ago

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.

[–] matsdis@piefed.social 20 points 1 day ago* (last edited 1 day ago)

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.

[–] cmnybo@discuss.tchncs.de 12 points 1 day ago

Mumble will do all of that except screen sharing. Only the server has to deal with NAT.

[–] Creat@discuss.tchncs.de 1 points 1 day ago (1 children)

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.

[–] early_riser@lemmy.world 1 points 16 hours ago

Or we could finally rip off the bandaid and move to IPv6

[–] spicehoarder@lemmy.zip 0 points 2 days ago

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.