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.
┌───────────┐
Voice/Text │ TeamSpeak │ Voice/Text
┌──────────┐ ───────> │ Server │ ───────> ┌──────────┐
│ Person A │ │ │ │ Person B │
└─────────┮┙──────────│┄┄┄┄┄┄┄┄┄┄┄│──────────┕┭─────────┘
| | └───────────┘ │ ∧
| | URL URL │ │
│ └────────── ┌───────────┐ <─────────┘ │
└───────────> │centralized│ ────────────┘
Image Upload │ myTS │ Image Download
└───────────┘
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 |
|
|
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.
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.
- Some other way.