I host my own TS3 server. It uses significantly less resources than the Discord client, has better audio (at least my friends sound better) and data is not going to Discord for whatever they're using data for. In case there's an issues with my Teamspeak server, I can solve it, instead of waiting for Discord.

I play games with my friends and girlfriend sometimes, I host a TS3 server to talk to each other for several reasons -

1) Voice data stays with us, not yet again some other company 2) The TS Client is slim, lightweight and uses little resources while the Discord client is absolutely horrid, sluggish and quite the memory hog 3) TS has far superior voice quality (subjectively) and latency (due to the server being close)

My group of friends still uses Mumble for talking to each other. It is hosted on our own server. It has transports to all sorts of messengers.

I use discord for some things, but only from a browser. Wouldn't want to use it professionally, although it is relatively decent.

Speech quality is far better on mumble with less latency, because the server is in near proximity.

edit: Don't know about Mumbles text chat, it is rarely used.

Same thing I've always used it for, talking to people I play games with.

Teamspeak never stopped working so there was never a reason to switch to anything else.

> Teamspeak never stopped working

Hah, I have a different experience: my Teamspeak server literally stopped working once they started requiring a license key even for self-hosted instances. I scrapped the server entirely and switched to Mumble.

> Teamspeak never stopped working

Ah, so your circle of friends does not include people with messed up audio. Teamspeak happily passes on whatever it got as input. Discord does quite a bit of filtering, able to salvage legibility of some of my friends.

And.. why would solving the problem on server level instead of client level be favorable?

This is just another point for TS, frankly

It isn't a matter of server-side vs client-side (I have no clue what Discord does, but it does eat quite a bit of compute client-side), but of what we get out of the box.

There are various options in the client for this.

If you have complex communication needs then this generation of voice software is still the best you can get.

For example, I play a good amount of Eve Online and we have a lot of ACL shenanigans. First, you have your fleet's main channel where most of the membership is going to be. So far so good.

At the top of the list are leadership channels. These guys can talk to and hear their own fleet but with can also instantly page other people in leadership (corp leadership and also other fleet commanders).

Then at the bottom of the list are specific group sub-channels. For example, your scouts and your logistics players need a good amount of coordination with each other, so they will have a lil room where they can talk at each other without tying up comms for the main fleet or distracting leadership with stuff that isn't actionable to them.

Then you can add in a whole extra layer of complexity if you are part of an alliance with multiple corps in it.

You basically can't do that in discord unless you want to have to switch between different channels the entire time. It might sound overkill but if you have 90+ players in your fleet you cannot get away with 'just put everyone in a big room'.

My friends have a Teamspeak server so that's what I use when playing games with them. I prefer it over Discord because it's lightweight in comparison. Also for whatever reason, I can't seem to get the microphone sensitivity right in Discord the last few times I used it.

Talking to people who say they won't switch to Discord.

Both of them aren't probably going to use this either because <insert random tech tradeoff they believe is worth dying over>.

A lot of Tibia's gamers use it in Poland

I still use it for voice communication while gaming.