Categories
TeamSpeak

TeamSpeak 5.0.0-beta54.x – Announcements – TeamSpeak

Hello everyone!

Beta version 54 is now available to test! This week we fixed some bugs that were reported by the TS community and added a few new things for everyone to try out.

Hopefully the changelog and extra notes should explain the update well enough.

Full changelog

Fixes

Beta 54.1

  • Fixed possible crash when remote apps setting is active

Beta 54

  • Fixed server links not behaving correctly with some input
  • Fixed connecting indefinitely when using a privilege key on connect
  • Fixed bans not being created / no error being shown when user left server
  • Fixed whisper notifications appearing on every server rather than the server on which they happened

Additions

  • Added sound when receiving a whisper
  • Added context menu to user name on join, leave, kick and ban messages
  • Added notification center to the bell icon
  • Added ability for third party applications to be notified of TeamSpeak events
  • Changed default view to chat when selecting a channel

Remote application information

Information received by remote apps contain information regarding clients. These are currently numbers represented as a string, which correspond to the ClientProperties Enum.
The plan is to change this and make those keys descriptive strings rather than “10” for example.

Third party applications need to establish a connection and then send an authentication request as follows:

{
    type: 'auth';
    payload: {
        identifier: string; // com.myself.myapp
        version: string; // SemVer
        name: string; // Display name for UI
        description: string;
        content: {apiKey: string;};
    }
}

The user will then need to authorize the remote application in the settings before the application can receive any events.
Once the user has authorized the application, said application will start receiving events through its connection.

The remote application will receive the following response once it has been authorized. For future connections the application will need to send the authorization request with the apiKey set to the one received in the reply to the latest authorization request.

Authorization reply:

{
    type: 'auth';
    payload: {
        apiKey: string;
    }
}

Notes for this thread

  • Feedback as per always is welcome in this thread :smiley: . Issues that are not related to this update belong to it’s own thread.
  • We suggest to place your wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
  • We allow ourselves to delete all the off-topic posts from this thread.
Categories
TeamSpeak

TeamSpeak 5.0.0-beta54 – Announcements – TeamSpeak

Hello everyone!

Beta version 54 is now available to test! This week we fixed some bugs that were reported by the TS community and added a few new things for everyone to try out.

Hopefully the changelog and extra notes should explain the update well enough.

Full changelog

Fixes

  • Fixed server links not behaving correctly with some input
  • Fixed connecting indefinitely when using a privilege key on connect
  • Fixed bans not being created / no error being shown when user left server
  • Fixed whisper notifications appearing on every server rather than the server on which they happened

Additions

  • Added sound when receiving a whisper
  • Added context menu to user name on join, leave, kick and ban messages
  • Added notification center to the bell icon
  • Added ability for third party applications to be notified of TeamSpeak events
  • Changed default view to chat when selecting a channel

Remote application information

Information received by remote apps contain information regarding clients. These are currently numbers represented as a string, which correspond to the ClientProperties Enum.
The plan is to change this and make those keys descriptive strings rather than “10” for example.

Third party applications need to establish a connection and then send an authentication request as follows:

{
    type: 'auth';
    payload: {
        identifier: string; // com.myself.myapp
        version: string; // SemVer
        name: string; // Display name for UI
        description: string;
        content: {apiKey: string;};
    }
}

The user will then need to authorize the remote application in the settings before the application can receive any events.
Once the user has authorized the application, said application will start receiving events through its connection.

The remote application will receive the following response once it has been authorized. For future connections the application will need to send the authorization request with the apiKey set to the one received in the reply to the latest authorization request.

Authorization reply:

{
    type: 'auth';
    payload: {
        apiKey: string;
    }
}

Notes for this thread

  • Feedback as per always is welcome in this thread :smiley: . Issues that are not related to this update belong to it’s own thread.
  • We suggest to place your wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
  • We allow ourselves to delete all the off-topic posts from this thread.
Categories
TeamSpeak

Server 3.13.5 – Announcements – TeamSpeak

Server 3.13.5 did left his beta stage and is now available as a stable version.

This version will fix some crashes which got reported from the community and some hosts.
And it improves the performance when multiple clients connect to server at the same time (like after a timeout or server restart etc.)

Changelog

Server Release 3.13.5 18 May 2021

Fixed

  • Multiple ways to crash server on virtual server shutdown.
  • Performance increase when many clients log in at the same time.
  • Fix crash in HTTP query.
  • Fix crash on Windows during startup.
  • Fix HTTP api key creation issue when using postgresql as DB.

A docker version should be available within the next 48 hours.


Notes for this thread

  • Feedback as per always is always welcome in this thread :smiley: . Issues that are not related to this update belong to it’s own thread.
  • We suggest to place wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
  • We allow ourselves to delete all the off-topic posts from this thread.
Categories
TeamSpeak

TeamSpeak 5.0.0-beta53 – Announcements – TeamSpeak

Howdyyyy :cow:

Beta version 53 is now available.
This week we fixed some bugs that got reported and did go one with work on file transfers.

I think this time the change log explains itself.
i have no information to add here. Feel free to ask If there are questions related to this release left.

Full changelog

  • Added toggles for file transfer speed limits, rather than setting the limit to zero
  • Fixed issues which caused wrong file transfer speed limits to apply in some scenarios
  • Fixed not automatically scrolling up when dragging items to the top of the visible area in server tree and file browser
  • Fixed not respecting previous window state when restoring using the systray icon rather than the taskbar icon
  • Fixed ban client context menu months/years option not banning for the expected amount of time
  • Fixed teamspeak:// links not being shown as invite in chats
  • Changed Share Invite Link to create teamspeak:// links
  • Changed file transfer speed limits to be global

Known

Notes for this thread

  • Feedback as per always is always welcome in this thread :smiley: . Issues that are not related to this update belong to it’s own thread.
  • We suggest to place wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
  • We allow ourselves to delete all the off-topic posts from this thread.
Categories
TeamSpeak

Alpha Testing? – Announcements – TeamSpeak

I would love to apply to test releases!

Overall, how long have you used TeamSpeak for? (any version)

Since 2006, TeamSpeak 2, and a constant user the whole time.

What OS/OS’s are you currently using?

Currently using Windows 10 mainly, but I can test on Linux (Ubuntu) for the desktop. All my servers run CentOS 7 and Ubuntu 20.04 if you’re also looking to test server releases.

Are you currently a server owner, an active user (but don’t run your own server), inactive, or a mixture of the prior?

Server owner and active user, with users who would also be willing to test.

On a scale of 1-5 (1 being low and 5 being the best), how would you score your technical knowledge on TS?

5, I would hope so after 15 years! I’ve coded numerous extensions for the servers I own and am very familiar with the Server Query system.

Optional question – If you could add something that doesn’t exist on TS currently, what would it be and why?

My most wanted feature is the ability to expand links posted in the chat, like the way Telegram/Slack does it. My second choice would be a web client.

Categories
TeamSpeak

TeamSpeak 5.0.0-beta52.x – Announcements – TeamSpeak

Hello :upside_down_face: a new beta update was released.
And this is what we’ve added and changed since the last client, along with some bug fixes.

  • We decided to change the invite protocol to teamspeak://
    The invite via tsserver:// won’t work any longer work in TS5!
  • We added cid (for channel id as target) as optional invite parameter. We missed that in beta 51.

Here is an example where channel was replaced with cid as target.

teamspeak://example.com?port=9987&nickname=tester&password=secrets&cid=15&channelpassword=NotTellingYou&token=C3bcBHpSStQHFHc7UO89dKwhCSRkR7ysJN3HRTXr&addbookmark=Example%20Bookmark

  • Settings for file transfer bandwidth and parallel transfers got added to the Settings menu. There you also find the

Full changelog

* beta 52.1
* Fixed potential UI freeze on fresh installation when a member of big chats
* Fixed not attempting to connect to secondary addresses if the first one fails
*
* beta 52
* Renamed protocol from tsserver:// to teamspeak://
* Tweaked file transfer UI
* Added search to file transfer, allowing to search for files within the currently displayed folder
* Added sound notifications for whisper
* Fixed an issue with teamspeak links on Mac
* Fixed Open File not doing anything if the operating system does not know how to handle the file type
* Added settings for filetransfer speed and concurrent up/downloads
* Fixed markdown links not working correctly in some scenarios
* Fixed issues connecting to a server with a privilege key
* Fixed invite urls containing the port when not needed
* Fixed not seeing server and channel groups in some rare cases

Known

  • Bandwidth setting applies really high numbers when values like 2,5 Gbps got set before. This fix did not made it into beta 52.
  • Bandwidth default is 0 and means unlimited. We are still working on it and will add a setting to disable limitation for a better understanding.
  • teamspeak:// invite in chats are not converted but ts3server:// invites are.

Notes for this thread

  • Feedback as per always is always welcome in this thread :smiley: . Issues that are not related to this update belong to it’s own thread.
  • We suggest to place wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
  • We allow ourselves to delete all the off-topic posts from this thread.
Categories
TeamSpeak

TeamSpeak 5.0.0-beta52 – Announcements – TeamSpeak

Hello :upside_down_face: a new beta update was released.
And this is what we’ve added and changed since the last client, along with some bug fixes.

  • We decided to change the invite protocol to teamspeak://
    The invite via tsserver:// won’t work any longer work in TS5!
  • We added cid (for channel id as target) as optional invite parameter. We missed that in beta 51.

Here is an example where channel was replaced with cid as target.

teamspeak://example.com?port=9987&nickname=tester&password=secrets&cid=15&channelpassword=NotTellingYou&token=C3bcBHpSStQHFHc7UO89dKwhCSRkR7ysJN3HRTXr&addbookmark=Example%20Bookmark

  • Settings for file transfer bandwidth and parallel transfers got added to the Settings menu. There you also find the

Full changelog

* Renamed protocol from tsserver:// to teamspeak://
* Tweaked file transfer UI
* Added search to file transfer, allowing to search for files within the currently displayed folder
* Added sound notifications for whisper
* Fixed an issue with teamspeak links on Mac
* Fixed Open File not doing anything if the operating system does not know how to handle the file type
* Added settings for filetransfer speed and concurrent up/downloads
* Fixed markdown links not working correctly in some scenarios
* Fixed issues connecting to a server with a privilege key
* Fixed invite urls containing the port when not needed
* Fixed not seeing server and channel groups in some rare cases

Known

  • Bandwidth setting applies really high numbers when values like 2,5 Gbps got set before. This fix did not made it into beta 52.
  • Bandwidth default is 0 and means unlimited. We are still working on it and will add a setting to disable limitation for a better understanding.

Notes for this thread

  • Feedback as per always is always welcome in this thread :smiley: . Issues that are not related to this update belong to it’s own thread.
  • We suggest to place wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
  • We allow ourselves to delete all the off-topic posts from this thread.