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?

  • frongt@lemmy.zip
    link
    fedilink
    English
    arrow-up
    84
    ·
    18 hours ago

    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.

    • Creat@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 hours ago

      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.

    • lambalicious@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      22
      ·
      17 hours ago

      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
        link
        fedilink
        English
        arrow-up
        15
        arrow-down
        1
        ·
        15 hours ago

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

        • lambalicious@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          2
          ·
          8 hours 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
      link
      fedilink
      English
      arrow-up
      16
      ·
      edit-2
      16 hours 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.

    • Spice Hoarder@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      17 hours 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.