TeamTalk v5.3.0.4914 now with profiles and channel bans

A couple of new features have been added to the upcoming TeamTalk v5.3 release. In this latest beta version you can now ban users from joining a channel. Previously it was only possible to ban people from the entire server. To ban someone you must either have a user account with ban ability or be operator of the channel. To remove the ban again you can clickChannels menu-item and then “Banned Users from Channel”.

Also in the new v5.3 beta release it’s possible to use profiles when you run multiple TeamTalk instances. When you create a new TeamTalk instance from the Client-menu you’ll be asked to either choose an existing profile or create a new one.

New Feature List

Default Qt client

  • Facebook web-login for Facebook enabled TeamTalk servers
  • Profiles for running multiple TeamTalk clients (Ctrl+N)
  • Ban users from channel
  • Ban option for username and/or IP-address
  • Option to ban subnets using wildcards, e.g. 192.168.0.*
  • Abuse prevention tab in user account administration
  • OPUS audio codec updated to v1.2.1
  • WebM (VPX) video codec updated to v1.6.1
  • TeamTalk client for Windows no longer supports Windows XP
  • TeamTalk clients for Windows updated to Qt v5.8
  • TeamTalk clients for Debian Linux updated to Debian GNU/Linux 9 (stretch) and Qt v5.7 (PTT behaviour changed)
  • TeamTalk client for Mac requires minimum macOS 10.9 (Mavericks)

Accessible Windows client:

  • Facebook web-login for Facebook enabled TeamTalk servers
  • Profiles for running multiple TeamTalk clients (Ctrl+N)
  • Ban users from channel
  • Ban option for username and/or IP-address
  • Abuse prevention tab in user account administration
  • Tell operator state using Ctrl+G
  • Send text message from Online Users dialog
  • Move multiple users (Store for Move menu-item)
  • Arabic, German, Turkish, Chinese
  • OPUS audio codec updated to v1.2.1
  • WebM (VPX) video codec updated to v1.6.1
  • Windows XP is no longer supported

Android client:

  • Facebook web-login for Facebook enabled TeamTalk servers
  • Added Indonesian language thanks to Muhammad Gagah
  • OPUS audio codec updated to v1.2.1
  • WebM (VPX) video codec updated to v1.6.1

iOS client:

  • Facebook web-login for Facebook enabled TeamTalk servers
  • OPUS audio codec updated to v1.2.1

Server:

  • Facebook user authentication
  • Ban users from channel
  • Ban option for username and/or IP-address
  • Fixed brute force login prevention using ban feature
  • Limit number of issued commands by clients
  • TeamTalk server for Windows no longer supports Windows XP
  • TeamTalk server for Mac requires minimum macOS 10.9 (Mavericks)
  • TeamTalk server for Debian Linux updated to Debian GNU/Linux 9 (stretch)
  • TeamTalk server Raspberry Pi updated to Raspbian GNU/Linux 9 (stretch)

Download TeamTalk v5.3.0.4914

TeamTalk v5.3.0.4914 for Windows 7/8/10

TeamTalk v5.3.0.4914 Classic (Portable) for Windows 7/8/10

TeamTalk v5.3.0.4914 for macOS 10.9+

TeamTalk v5.3.0.4914 for Debian 9 (x86)

TeamTalk v5.3.0.4914 for Debian 9 (x86_64)

TeamTalk v5.3.0.4914 for for CentOS 7 (x86_64)

16 Comments

  1. Hi, since you are adding new features, you should add a way to ban hardware, because there are people in servers changing ip’s, and the hardware its not so easily to change. Thanks!

    • One of the reasons I’ve added Facebook login is to have a central login system. If you ban the user’s Facebook account then they cannot login. Not with other hardware or another IP-address.

  2. Facebook login was working alright in the previous .4911 build. However, in this .4914, the screen reader would stop speaking after I choose Facebook as username.

  3. Hi, I know it is very hard to code, but here’s a suggestion, for the next major version (future version) of TeamTalk, maybee version 6, if that’s the tyme to code it. As TeamTalk has 2 clients, the qt client and the accesibility client, can you add a WX-Widgets or WX-Python clients? This will have the following: 1: Support for any user, no mather the impairment, sight, low vision, ETC. To be used worldwide. 2: More internationalisation: WX-Widgets, for the translation of applications, uses Po-Edit (available from http://poedit.net) which is a software to translate an application into other languages, using .pot files for the template, .po files for the translation, and .mo files for the compilated translation which TeamTalk uses. Linguisticly it provides more presition on the language, as more translations, as for example: the about dialog, and other dialogs. Also in this method, languages will now show the ISO-639 code, instead of the language name in the file, EG: for Spanish will be “es”, for english should be “en”, etc. Well, I thawght I was going to doo it, but well, hope you are well.

  4. The channel ban new feature is a good idea!

    I have another idea.
    Can you add a function wherewith I can hide an user on a server?

    I write an example, I think I can’t write the idea correct:)
    So there is a server where anonymous can see all users in all channel. But I’d like to hide a specific user account’s user from users and only show for admins.

    Is it an operable idea?

    • Currently there’s an option where Default users cannot see people in other channels whereas Admin can see everyone. Can’t that be used instead?

      • This option was the best, but now I realised that if users can see each other they can send messages.
        But some users want use the server as hidden from other users exception admins.

  5. To you, if I imvent a time machine I know what I’m going to do. Infact, We need a unified client, based on WX. As for translation we use PoEdit.

Leave a Reply

Your email address will not be published.


*