I need you all to understand that Teamspeak is still nowhere near an alternative to Discord

General Discussion
1

Adding servers and adding contacts was fine enough, but making a muted AFK channel by “setting Talk Power to a high number, like 50 or something” is insane. It also seems I’m not able to see a chat channel without joining its accompanying voice channel. If that’s the case, that honestly sucks.

I can’t upload an image as a server icon, I don’t know why, it just doesn’t appear after I’ve tried to upload, and no error message. I can’t find any in the 3 logs/chats I’m advised to check, nothing in Server Log (Events?), Server Chat, and I don’t know where Client Log is. I don’t know what the issue could be, if the issue is permissions. My “Upload Quota per Client (MByte)” as a guest promoted to Server Admin is "-1”. I don’t know what that means. Someone mentioned “sounds like the required port is blocked , make sure all required ports is open”, I don’t know what ports they’re talking about or where to find and open them. (Can't get my server icons to upload)

Along these specific recent issues, there are a myriad of puzzling things I’ve encountered in the last 24 hours that I can’t quite put my finger on, or frankly even recall.

The whole client is deeply arcane, you might prefer it but it’s not going to be an alternative, we’ll see where the refugees go when they reject TeamSpeak again. Likely a new company with the same end-goal, and another ship to jump in 10 years if circumstances allow.

I recently saw the same design and user preferences kill Lemmy as a Reddit alternative. It had good momentum going but users and administrators decided it wanted to stay small, and wanted to leave international large scale forum power in the hands of Reddit. Lemm.ee was shut down and now most Lemmy instances require an application to join.

Lemmy didn’t want the role it seemed destined for.
I’m guessing TeamSpeak is the same. It does not want the role.

I expect some denial in response to this, but largely criticism of the mere fact I bring it up combined with a resigned confirmation that yes, TeamSpeak and its userbase does not want to replace Discord and does not want to capture any large percentage of that userbase. That TeamSpeak wants to stay arcane. That TeamSpeak will still prefer to define muted AFK channels by a talk power set too high to talk.

2 Likes
2

You need to change “Icon Max file size” permission. Stock value is really low, something like 1KB. That’s why your uploaded icon doesn’t show up.

But yeah, permissions are overly complicated. Sure you can micro-manage lots of things with permissions, but basic permissions should be more user friendly.

Also global chats doesn’t exist, so you need to join voice channel to see chat. Global chat with server side memory (so you can see posted messages even if you weren’t online then) is a must have feature imo.

2 Likes
3

Thank you, I found it under Permissions > Server Admin, then searched for icon. I set it to 250 000. Now we have a server icon, and a few channel icons.

We’ll continue to attempt the transition.

We’ll see if TeamSpeak catches any important UX fixes before the waves of Discord subside and the opportunity is gone.

Likely it’s too late as it wasn’t in a suitable state when the exodus started, any hasty attempts will only make the client worse off.

(Btw, if anyone knows how to make the AFK channel actually mute for server admins I’d like to know. Setting Talk Power to 50 apparently didn’t work, I could still talk, so I spammed in 9’s until it maxed out at “9 007 199 254 740 991” and it still didn’t work. (That number changed to -1 now that I checked it again, guess that means -1 is infinite/maximum.))

Edit: Apparently in TeamSpeak 3 default Server Admin Talk Power was 75, idk if that’s still the case with TeamSpeak 6 but if it is, I don’t understand what the issue is.

Maybe my icon still shows mic input even when effectively muted through Talk Power.

Edit 2: Someone else got on to test, Talk Power 100 works to make an AFK/Muted channel.