Neat, I might check out Slack. Kinda annoys me how every workspace has its own login and just find chat apps somewhat distracting to run but I know a lot of pro

Neat, I might check out Slack. Kinda annoys me how every workspace has its own login and just find chat apps somewhat distracting to run but I know a lot of projects use Slack. I'm more of a Node and Typescript person though, but I know Golang is popular. I want to try to run babylon.js on the server side using its nullEngine to be authoritative. Still doing a lot of research though, so not sure if it will end up being a actual project. There was another project in Go I came across relating to WASM too that looked interesting. I know some projects or companies they are a polyglots though, whoever starts a new project picks whatever, but I'd prefer to limit things 1 or 2 languages on the backend as I think code reuse and would make it more maintainable. Like if it grows from an idea to a company, seems like having everyone on one tech helps with hiring and moving around resources. But I feel whatever you pick probably going to be locked into it for a while, like picking the right database but I know some projects run 2 or 3 databases... Social functions might use one, billing might be another one, search is another one. But yeah I liked WebRTC for voice for sure, but wanted to use it for other parts of the system too for the instance simulations to be able to connect to each other directly, but I guess I could always just use raw IPs too but it seemed like WebRTC gives you some things built-in for free like securing the data channels. I was thinking if I used WebRTC for voice only, then all I'd need to do is write some sort of API running inside of the cluster and just run the WebRTC servers outside of the cluster, since wanting to mix the audio on the servers to cut down on bandwidth to users, and also increase privacy a bit for users.