You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your suggestion related to a problem? Please describe.
When running a Matrix Element on a server, storing media can chew up bandwidth and drive space, especially if you're not integrating AWS or Backblaze into your self-hosted deployment.
Describe the solution you'd like
An optional button to compress media prior to upload on the client.
Describe alternatives you've considered
Considered (also) running a script on the server to compress images through many of the available libraries... that's probably also a good idea for self-hosting too.
Additional context
Proposed UX flow:
Suggest using the following fast, popular library:
Suggest preselected settings for user to reduce cognitive load of choosing compression amount:
compression: .80
max width 2550px (8.5" @ 300 DPI)
max height 3300px (11" @ 300 DPI)
Is your suggestion related to a problem? Please describe.
When running a Matrix Element on a server, storing media can chew up bandwidth and drive space, especially if you're not integrating AWS or Backblaze into your self-hosted deployment.
Describe the solution you'd like
An optional button to compress media prior to upload on the client.
Describe alternatives you've considered
Considered (also) running a script on the server to compress images through many of the available libraries... that's probably also a good idea for self-hosting too.
Additional context
Proposed UX flow:
Suggest using the following fast, popular library:
https://www.npmjs.com/package/client-compress
Test here: https://davidmoodie.com/client-compress/
Suggest preselected settings for user to reduce cognitive load of choosing compression amount:
compression: .80
max width 2550px (8.5" @ 300 DPI)
max height 3300px (11" @ 300 DPI)
Compressing other media (video, audio) harder, but possible with ffmpeg.wasm: https://github.com/ffmpegwasm/ffmpeg.wasm.
The text was updated successfully, but these errors were encountered: