It’s been a long time since the last release of TeamTalk so there’s many new features and bug fixes in TeamTalk v5.18.
To try out the latest features during beta testing be sure to enable beta update notifications in Preferences -> Display-tab.
Go to the Downloads section to get the TeamTalk v5.18 release.
New Features and Bug Fixes
Corentin Bacqué-Cazenave and new contributor Amir Mahdi have been busy so there’s a long list of improvements:
- Default Qt Client
- Media tab in main window for controlling media file streaming
- Support “{username}” variable for majority of TTS and status events related to user action
- Indication when user is sharing desktop in channel list
- Ability to restore all custom Text-To-Speech and status bar events to default values
- All byte sizes converted to local format
- Option to use TeamTalk Sound Output device for default sound event playback mode
- Option to choose bitween text or emoji for user and channel info in channel list
- Last login time shown in “User Accounts” dialog
- Ability to sort by “Last Login Time” in “User Accounts” dialog
- Ability to send toast notifications on Linux and Windows
- Ability to change chat history to list view in “Preferences” dialog
- Improved “Server Properties” and “Channel” dialog accessibility
- Nickname and Last Joined Channel are now stored in .tt file
- WebRTC updated from r4332 to r6818
- Qt updated to 6.9.0 on macOS and Windows
- OPUS updated to v1.5.2
- Ability to custom chat templates
- Remove option “Timestamp messages”, use custom templates instead
- Ask to retranslate Text-To-Speech events and status messages on language change
- Fixed gender changed from female to male when migrating to 5.17 release
- Fixed sound events disabled when migrating to 5.17 release
- Fixed language not set at first start
- Fixed OPUS DTX mode sending too big packets when variable bitrate mode (VBR) was disabled
- Fixed ask to use default sounds pack at every language change (will be asked one last time)
- Fixed untranslated status message on file deletion
- Android Client
- Replaced turn up/down buttons for speaker volume, microphone gain and voice activation level with sliders
- Added popup menu actions in Server List dialog
- Added “Message” and “User properties” user menu actions in channel list tab
- Ability to export each server in to a .tt file separately
- Nickname and Last Joined Channel are now stored in .tt file
- Broadcast messages, users logged in, and users logged out are now shown in the chat list
- Added the ability to send broadcast messages
- Ability to select/deselect user for move to other channel
- Simplified labels in User Properties dialog
- Fixed speaker not being enabled again when voice activation option was disabled
- IP address, user ID and status message are now in “User Properties” dialog
- Added missing labels for sliders in audio codec configuration
- The labels in Main Window and User Properties dialog no longer have duplicate texts
- Minimum supported is now Android v8.1 (Oreo)
- WebRTC updated from r4332 to r6818
- OPUS updated to v1.5.2
- iOS Client
- WebRTC updated from r4332 to r6818
- OPUS updated to v1.5.2
So when are we gunna see a more secure server protocol? Passwords no longer being stored in plain text and user account management being implemented on IOS? It’s 2025 and this day in age, passwords should, not, be stored in plain texts for anyone! There’s gotta be a better way of handling this. have user info be stored in mysql databases that’ll be your best bet and hash them of course. This also will mean that server admins will need to know how to use mysql or something to the equivalent of to stor said info. Hell, have it to where the server can connect to said database of your choosing on setup and create the necessary tables. Again, it’s, 2025! This unsecure stuff is laughable. Back in the day, fine, not now and this needs to be brought up with the times!
Just looked and there is literally a mysql driver for QT. I have no idea how to work with it because I don’t code in QT. I’m a web dev. Not an app dev Lol but something like this aught to be doable at least.
but you’re not left with out solootion, you can use bearware.dk account and allow users to connect using their bearware accounts, this way their passwords are completely managed by nobody except them selves. If we do this, then bearware loggin feature would become completely useless. So, we’ll keep it like this, to give people choice, between simple plane text or bearware.dk user account. Personally i’d choose plane text so I don’t have to deal with hash passwords, and all this stuf. teamtalk is known to be simple and really useful at the same time.
hi.
about passwords, I think we’ve already told this a couple times, that it’s not gonna change. It will stay as is, for users who likes to controle their server like this, restoring someone’s password from server’s xml file etc, for example.
about user accounts managements, please be pationt, we are investigating. First it’ll be implemented for android, and then possibly others.
Mysql for passwords would get messy for things like restoring and moving servers, version-controlling configuration files and thus accounts, etc. I think encrypting passwords in the xml file would make a lot more sense, if we do anything in this area; and even that will break a number of long-standing utilities (and I don’t mean just mine lol). Any solution that increases file count per server will be a lot of fun, sarcastically speaking, for the folks that run 50 and more servers on one Linux box.
Encripting is already available in pro server. And about encripting server’s xml’s files, it wouldn’t be a good idea, Because we can no longer simply open the xml in notepad and see the data, usernames, passwords if a user wants their passwords restored for them, etc.
For clarity: I was suggesting that just the password value be encrypted into something unreadable, not the entire xml file. The pro server encrypts communications but not the stored password. But again, I think that would break a few things out there that use passwords in their current form. Also, and I did not say this part already: It is difficult to hide something in an open-source project, because the code used to hide it can be read. It just becomes a little less obvious.
exactly, it’s just best to keep it as it is. Teamtalk is open source anyway, who ever wants they can implement their own client or server as they wish how they want it to look like. this is the actual project, and it’s just best as it is. Sometimes people give some suggestions that makes the app complicated. for example, we already can protect channels with passwords, and stil some people are requesting suggestions about public and private channels, being able to invite users to channels, etc, wel, that’s too much. You can just give your channel’s password to a user, and then just change it as soon as they join. The point of teamtalk is to be simple like this.
Hello, I downloaded the Mac version and it doesn’t work properly. When I connect to a server, it closes automatically. I’m on macOS 15.4.1 with VoiceOver enabled
Hi, same on my Mac, running same OS-Version. Even worse: After installation, I can’t launch teamtalk at all. Voice-Over is permanently busy and doesn’t display any window-control.
Wow, great features however too bad Since it’s 2025 I got surprised The Android version of Teamtalk has no features to view the banlist, viewing user accounts and creating a new accounts and editing the server properties, changing status message, and also a server version so it’ll be possible to create a serveron an android device, since it’s 100% possible to be emplimented if the development is active on it since noticed ain’t the case anymore, Teamtalk 5 droid lacks a lot of features and it’s too buggy compaired to the windows client, also no wonder The IOS Client too
hi. I’m really sorry about that what you’ve gon throo when using teamtalk android all these years. But the good news is that from now on, i’m the developer and supporter of teamtalk android, and as you see, many bugs have been fixed in 5.18. I wanted to bring all the features you mentioned to 5.18 already, but the main developer releaced the 5.18 already because it was a long time since 5.17 was releaced. But don’t worry, we’ll have a 5.18.1 releace soon, which will contane all the features you were expecting in teamtalk android. And any bug you know that I mite have missed to fix, please let me know, i’ll work on it.