This would be the perfect time for someone to throw up a nice UI for a webrtc based voice chat platform in the browser. Nothing to install, no crazy permission/server setup. Just create a room and invite your friends. Boom, team based voice chat.

So, this actually works pretty great. If it had integrated search, and the ability to add tags, and integrated favicons, people would probably use it as is.

But I’m a bit lost which approach and tools to use without exposing and making my NAS vulnerable on the internet.

You’re looking for a reverse proxy;

*.domian.dev {
        encode zstd gzip
        @jelly host jelly.domian.dev
        handle @jelly {
                reverse_proxy {selfhost_ip}:{port}
        }
        @ping host ping.domian.dev
        handle @ping {
                respond "pong!"
        }
}

Running caddy like this directly connects your jelly.domain.dev domain to your selfhost ip on a specific port. From within your selfhost you ensure that you’re only allowing in the IP of the VPS, so no one can else can directly connect.

Works great. I use this myself. I have a local NAS (with media) and run a jellyfin server from my PC (to use my GPU for transcoding). The jellyfin server only allows 1 remote IP (my VPS), and local connections. The local jellyfin server can be accessed via my domain at jelly.domain.dev.

It never made sense to me how popular discord was to begin with.

We’re too dependent on a technology that we spent tens of billions of dollars researching and perfecting over decades of research!

Possibly the dumbest statement I’ve heard this week.