TeamTalk v5.15 is now ready for download. Many thanks to the people helping out! Remember that you can become a TeamTalk beta tester by checking the “beta software updates” in Preferences dialog:
New Features and Bug Fixes
As you may have noticed there has been a lot of spamming of TeamTalk servers (mainly politically motivated) over the last few months. Therefore a lot of efforts have been put into prevent spamming. TeamTalk Pro Server owners can request to enable the SpamBot on their servers. This greatly reduces spamming.
Here’s an overview of the new features and bug fixes:
- Default Qt Client
- PulseAudio support on Ubuntu 22
- User right to prevent private text messages
- User right to prevent channel text messages
- Added Korean language
- Added Persian language
- Support for 320 KBit MP3 recording (Windows only)
- Support for banning IP-address as subnet, e.g. 192.168.0.0/24 or 2a02:09b0:402b:eed8::/63
- Username of user creating a ban is visible in “Banned Users” dialog
- Multi selection in Banned Users dialog
- Username or IP-address of current selection is shown in text box in “Banned Users” dialog
- Pressing Enter in text box of “Banned Users” dialog will add new ban
- Kick/Ban From Server now in context menu of Online Users dialog
- Client version shown in “View User Information” dialog
- Option in Display-tab to disable user and channel icons
- Option in Text-To-Speech-tab to configure whether to try SAPI when screenreader is not available
- Label of files list now includes channel path
- Fixed state of “Close when completed” checkbox on “Transfer file” dialog
- Fixed files count not announced for non admin users when pressing CTRL+G on non current channel
- Fixed users still showning channel in Online Users dialog
- Changed to Qt 6.6.1 on macOS and Windows
- Server
- User right to prevent private text messages
- User right to prevent channel text messages
- Support for banning IP-address as subnet, e.g. 192.168.0.0/24 or 2a02:09b0:402b:eed8::/63
- Creator of ban is stored
Hello,
We should have an option to hash of encrypt all passwords in the xml or an option to encrypt the xml on proserver.
I suggest you use BearWare.dk WebLogin instead.