Currently images sent to a chat on a TeamSpeak server are send not through the server but uploaded to myTeamSpeak and a link to the image is automatically send through the chat. It roughly works like this.
This is limited to 5 MB per file and requires myTeamSpeak features to be enabled when connecting to a server.
TeamSpeak has a system where users can upload and share files via the file transfer protocol. This is not inherently limited but can be configured with permissions. Users can create a direct link to any uploaded file and share that. (This all existed back for TeamSpeak 3 already.)
My question now is shouldn’t files be uploaded to the server you are connected to instead of some other centralized server?
From my point of view these are to pros/cons of each system:
File Transfer Approach
myTeamSpeak Approach
+ Does not require myTS account
+ Works in offline LAN settings
+ Easily configurable fize size limits
+ Files can already be downloaded
+ while still being uploaded.
+ File retention could be configured
- Requires permissions to up/download
- Bandwidth usage for server hoster
- May lead to confusion¹
- Requires myTS account
- Needs to be always online
- Fixed limit at 5MB (currently)
- Files need to finish uploading
- before they can be downloaded.
- Files are gone after 30 days.
+ Can be used reguardless of permissions.
+ Bandwidth usage for TeamSpeak
+ Just works
1: E.g. if some users have reached their file download quota or no permission to download files at all from the server they will not be able to view images send through the chat. Though one might argue that setting up servers with proper permissions is up the the administrator and treat this as expected behaviour.
With all that:
Keep every as is - files through myTS.
Switch to server file transfer fully.
Make it configurable.
0voters
In case it was made configurable, where would you expect this configuration to take place?
On a server basis. Administrators should be able to set how files are send on their server.
On the sender side. Each user should be able to select whether they trust the server hoster or TeamSpeak.
yeah, you’re right. doesnt make sense with the current system. I think someone could achieve a plugin that does this.
but this should be a feature by default. I hope it changes that way for the better. I saw a post from a staff member saying it would be a step back without mentioning why.
I’ve been thinking more about this, and honestly I think it should be chosen by the client. If the client prefers to upload to the server (only if permissions permit them to do so), then they need to deal with the additional quota usage of the server, the admins set file limit, and permissions. otherwise, let us upload to teamspeak for simplicity by default.
on the poll, I am the “Some other way” voter for the sending configuration, since I believe there should be a mix of both sender and server configurables.
With the new server now officially supporting S3 file transfer allowing the option to send chat attachments not through myTS but the server itself seems even more of a no-brainer.
Can we expect any news on this soon?
The implementation on the client side remains the same (e.g., checking permissions, initiating the file transfer, and notifying other users that a picture is sent) and S3 does not change anything in this regard.
However, this is a feature we would like to address in the future, when capacity allows and if priorities align.
(with the recent discord hubub), I feel this question is very important. Letting people host screenshots and clips in the server themselves rather than centralized in myTeamspeak.
It would make the responsibilities clearer, each server could set and enforce its own rules about around what content is allowed (and local laws of that server host).
I feel the same. We often have issues with Discord (most of the times due to connectivity problems between Telekom and Cloudflare) and came back to TeamSpeak for comms but we still rely on Discord to communicate in text and send stuff.
Hosting text and images on the server itself that could be accessible from multiple clients by the same user would make TeamSpeak a complete replacement for such usecases.
Currently I host a beta TS6 server to actively test and I am more than happy to give feedback on updates and such if wanted.
As I would lime to host entirely on my own hardware, I would love for the configuration to point towards and ingest for a file server that documents can be stored and retrieved from for the hosted TS server. Default can point towards the myTeamSpeak ingress as it does now. This way the embedded links can still work by pointing back to the configured file server. Either a specific implementation or even if its an ftp / sftp server. Idk if it sounds crazy but almost having a matrix like back end for messages to support images and persistent text would be really nice.
It would, while more involved, be great to have a file server that allows support for:
Disappearing file timers / messages
External / User uploadable emotes
Voice recording / sound files
These are optional of course, but wanted to throw out some ideas if we were walking into the realm of an Owner hosted file server that the TS server can point towards as its resource manager.
First off, sorry if this should be in server, could not decide where this should be.
When I self host something I intend it to ALL be self hosted.
It would seem that images that are just plopped in the text chat are not stored on the server, but some Teamspeak server. Please allow ALL files, Images, text logs, the like to be stored on the server. Ideally nothing is done or stored on Teamspeak servers.
P.S. it would also be nice if there was a server setting or the like that when a file is uploaded there is a notification in the relevant text chat.
As a workaround you can upload files to the server storage, right-click a channel and click Browse Files. There you can upload your files, copy the URL and send it in chat.
