It'd be really useful if you could use Teamspeak on devices like the Raspberry Pi which is ARM based but there are no ARM TS builds... so some ARM support for TS 5 would be nice. :D
Printable View
It'd be really useful if you could use Teamspeak on devices like the Raspberry Pi which is ARM based but there are no ARM TS builds... so some ARM support for TS 5 would be nice. :D
that would even be my most favorite function for running ts5 server on my raspi
There won't be a "ts5 server". The TeamSpeak 5 server software is called TeamSpeak 3.
Hello,
I must admit, I'm quite excited for TeamSpeak 5. I've always had little ideas for TeamSpeak, but never really submitted them, so here goes.
Further Hotkey support + native joystick / button box support:
What I mean by "Hotkey" support is add more possible key assignments, like "Modify Permission Value" I think this would be
really beneficial for larger servers, because when you make a server, you are often changing the same values, but modifying the
permission power (Also I think TS5, should keep the current permission system, or add an optional advanced / basic one).
Also Button Box / Joystick button support should 100% be native in TS5.
Better SDK (or more friendly one)
There should be easier implementation of bots (i.e server query), you should have a base api that can be expanded on (like
the current implementation), just don't make it difficult to implement, all of the current Wrappers are either over
complicated, or just don't work anymore.
(I'd say improve the client api, though I haven't messed with it yet so I can't really comment on it).
Improve the user interface (or allow further customization)
You guys should implement base themes, one's that are native with the client (like a Dark Theme, etc). And allow CSS to be
used for the UI. It would allow further modifications. I'm all for letting programmers handle it, but realistically you
want it to be more accessible for everyone (by this I mean don't make it in an addon form, make a easy to use selector).
Expand the offline messaging support
Offline messaging support works. I'd recommend using the current MyTeamSpeak implementation and include a messenger,
some people only use TeamSpeak, and it would be good to be able to message others without them having to join a server.
Expand the current implementation of MyTeamSpeak on servers
I've used TeamSpeak for years, and have never switched, but I think the idea of allowing users to implement MyTeamSpeak on the server end is useful, and a great idea. Expand the use of TeamSpeak, allow for custom commands, etc. Without using 3rd party stuff, like SinusBot, JTServerMod, etc. (What I mean by this, is expand the API on the server end more than ServerQuery.)
Addons
The "addon" download area should be put directly into the client. Having to have you're users goto an external site, then download a file from you're site, then have them install it, is a bit much (if you ask me), it would be much easier, and probably a lot faster if this "marketplace" was brought directly into TeamSpeak, and you didn't have to download it from the site, but rather you could download it directly from the client.
Permissions
This is gonna be a long one.
I love the current permission system to an extent. I think there are missing features. TeamSpeak's "basic" permission system doesn't to it for the majority. Which makes it not user friendly, which often turns people away. TS5 should have a basic permission system that works, and does everything the advanced one does, without complications. The advanced system on TS3 is great, and should be carried over to TS5 but should just give more options, mainly for the people who want to expand on the basic one.
Server Group Channel Permissions
TeamSpeak 3 has Client Channel Permissions, why not Server Group Channel Permissions? This would add SO many more options. Especially for the larger groups. Even if you guys don't implement everything else, PLEASE IMPLEMENT THIS.
Mobile
The mobile version of TeamSpeak should be free, why is the Desktop version free, and the mobile one not? It doesn't make much sense in my opinion.
-----------------------------------------------
Closing
Thanks for reading, these are just some of the ideas I could think off, and I'll probably have more that i'll submit.
Many of your points are about the server. The TeamSpeak 5 server is called TeamSpeak 3.
SDK and query are different things. If you don't like existing wrappers, make your own one like I did. Sadly, I have noone to blame if something doesn't work. :(Quote:
Originally Posted by JordanDev
TS3 skins are currently created using CSS.Quote:
Originally Posted by JordanDev
This was announced on gamescom.Quote:
Originally Posted by JordanDev
What "API on the server end"?Quote:
Originally Posted by JordanDev
Please update to TeamSpeak 3.1 or newer.Quote:
Originally Posted by JordanDev
If the "basic permission system [...] does everything", why would you need an advanced permission system? I don't get it.Quote:
Originally Posted by JordanDev
Beside that, the sentence "improve permission system" is not a good suggestion. Tell them how.
Backing this.Quote:
Originally Posted by JordanDev
I hope Teamspeak does away with these pointless numerical notations, and just call the product Teamspeak, nothing else is needed. I'm not talking about version numbers, just the whole Teamspeak 2/3 5 etc..Quote:
Originally Posted by numma_cway
I agree with:
andQuote:
Server Group Channel Permissions
TeamSpeak 3 has Client Channel Permissions, why not Server Group Channel Permissions? This would add SO many more options. Especially for the larger groups. Even if you guys don't implement everything else, PLEASE IMPLEMENT THIS.
Quote:
Mobile
The mobile version of TeamSpeak should be free, why is the Desktop version free, and the mobile one not? It doesn't make much sense in my opinion.
Probably some REST style interface. Would be nice, arguably better then the telnet query.Quote:
Originally Posted by numma_cway
I think a feature to share the screen would be great.
So TS5 will be just an update?
Anyway, I think that offline messages will be more useful with a popup when you open the client or join a server
Why exactly?Quote:
Originally Posted by fspower
Do you have a source for this?Quote:
Originally Posted by numma_cway
Add:
-ban for hardware id or an id that does not change over time and can not be changed
-can hide server message (<user x to deleted channel x>) related to a specific user («example a bot»)
everything can be changed, even the hardware idQuote:
Originally Posted by AndryGabry
they already said they wont do that and i understand why.Quote:
Originally Posted by AndryGabry
That would be nice to which server my friends are actually connected if I got them in friends list.
Greetings.
Then TeamSpeak would have to redevelop a complete friend system, simply add one as a friend and seeing where he is, is a bit creepy :rolleyes:
Teamspeak 3 has been out for like 10 yrs I think they've had more than enough time to upgrade and provide something better to gamers it's sad it took something like Discord to begin this, I doubt they would say it's because of that but let's all be honest here.Quote:
Originally Posted by DoloDE
Feature wise teamspeak isn't terrible, visually tho while the layout is great (I hate the layout of discord) everything is outdated, even channels to make them nice using *cspacer just to make some channels more organized all these need to be easier done.
Because it is easier and faster to use common HTTP libraries than to use telnet parsing. Including \r\n.Quote:
Originally Posted by numma_cway
removed unsupported language
English:
create an immutable / masquerable id and create a type of ban for that id, because it is not possible for one to restart the modem or use a proxy / vpn to evade the ban
Quote:
Originally Posted by MeltDownPlayer
I know that everything can be changed, I speak of a more complicated system to change, a system that does not allow an 8-year-old to go download software and break without even committing a bit, it does not have to be hardy hwid but at least something more substantial than the ip address
removed unsupported language
This is technically impossible.
Encrypt absolutely everything (including file transfer)
Can you provide a source for that claim?Quote:
Originally Posted by fspower
I would say using HTTP communication adds so much overhead that the performance would be equivalent (if not slightly worse) than a highly specialised and improved parser for a protocol?
However, I too think that upgrading to a less outdated technology for tool<->server communication would be a benifit. At least TLS should be supported in my opinion.
Easier: a oneliner curl call vs. multiple linesQuote:
Originally Posted by MarkL4YG
The "faster" is meant as faster development time, because you don't need wo waste time implementing a broken telnet interface. Performance would not be much different.
Also you can use the existing HTTP infrastructure. Basic Auth, TLS, Certificates, Reverse proxies like nginx.
It'd be really useful if you could use Teamspeak on devices like the Raspberry Pi which is ARM based but there are no ARM TS builds... so some ARM support for TS 5 would be nice.
I know this is more of a server side type of request but with respect to encryption I'd like to see the ability to import a cert chain, matched against the server's hostname, to be used for encryption.
I don't know how teamspeak handles voice encryption now without a certificate or chain of trust but it would make the encryption more robust I would think if we can use strong ciphers and forward secrecy.
On the topic of permissions:
The #1 thing I would like to see is better channel access permission options.
It is a pain to organize channels when access is determined on a >= basis. Some times I want only this one, or couple of groups to be able to join a specific channel. I cant give them more join power than another group, cause then they can join channels that I might have restricted for the other group, but then if I set it lower the other group can join this channel.
Edit: I get that channel groups exist, but that unnecessarily complicates things, especially when all we need to do is restrict access.
+1Quote:
Originally Posted by Col_Crunch
Channel group management sucks. Its more complicated because its an extra layer of permissions and is also kinda invisible and hard to manage.
Why not just utilize the server groups further and make it a easy "rock, paper, scissor" thing?
Channel X needs group A, B or G to join.
Channel Y can not be joined with groups C or D.
Hi guys,
After my first thread about this, I need to talk about it:
I think it would be very nice to have the opportunity to do video conferences on TS5.
And this simply, just in his channel with a button to activate his webcam.
Thank you, Hugo.
I think it would be a good feature, but it should be optional. The server administrator must be able to enable or disable this feature, since it will consume more server resources.
Just to be correct: You can already to that as nginx can tunnel any kind of TCP connection just fine. Even optionally disabling/enabling TLS encryption. Which I just added support for in my plugin framework by the way so that claim is tested :) .Quote:
Originally Posted by fspower
What we might really need later this year is the ability to disable all upload features in order to comply with new EU copyright laws.
I'd like to see the files folder instead be incorporated into the mysql database. That really is just a protection against me not moving the folder over and losing all previous icons during an upgrade.
Transifex for languages. Because russian is still awful.
Built in Volume control like this:
https://www.myteamspeak.com/addons/d...9-51dc224c5c27
But for example a better whitelist/Blacklist
Because at this plugin you can only write a few names before it's full. (Inputbox is static)
Server-Side Addons would be great for admins. Specially for Server-Wide bots (type in any channel and it answers, no matter where you are. It's a real mess right now because the bots must be in your channel).
Also: Python support! Python is evolving as the true winner of programming for some specific situations like AI or bots, so it would be great. Or I guess a REST API to deal with the teamspeak server easier than telnet.
Provide a certificate system to verify the servers you're connecting to
Also the ability to hide specific channels from users like in discord
Give server group specific permissions in specific channels.
Quote:
Originally Posted by Saelyth
I like both ideas!Quote:
Originally Posted by florian2833z
A Gui based on Qt Quick Controls 2.
This would make the gui more modern and allow for common code base between the mobile and the gui client.
Also extending the ui is much easier using QML.
Also there's currently TSDNS to discover Teamspeak servers on the target server. Would it be possible to instead send the requested server name when connecting like with http?
They dont use Qt in the new client anymore.Quote:
Originally Posted by Thaodan