Automatic media compression on upload, on by default

Storage of Media can be expensive. In fact Fluxer has that 3 year expiration date, so.

Automatic Image/video compression of uploaded images. This feature can branch from the singular uploaded media in the chat, to server-IMPOSED setting, which if branched more it expand to FORCE users to go through a process of compression of their media (every uploaded media must go through the process of compression in that specific server)

1. You can start by adding a setting on the user client side that handles this:

• "Do you want compression to be turned on as default for every media u upload?" (can be turned off in the singular Edit Attachment) ON/Off
• A setting to sub-choose if the compression must be on/off for image-only, video-only or both.

Note: [[ I suggest for Fluxer to have the compression of images-only to be set to ON as default, users can change it if they wish in the settings. It is a "dirty" move but storage can cost. ]]

2. Server-side settings, where the server admin choses if users are allowed to upload Uncompressed.

-"Force the compression of media?" On/Off (users cannot turn off compression in this server, if they want to upload the must compress) -same as above, image-only, video only, or both You can work out the details, for example when the image is too small already, less than 100kb or 200kb, maybe the compression isnt needed. If a video is 10mb, and 2-4 minutes long, and with a resolution of 450p, compression is NOT needed just based on these the first two parameters. It is to not overdo the compression time on the users, which takes time. A kind of video-size/video-duration parameter to see if it is worth to compress seems very fair.

Users dont care about the size of what they upload, nor do I. Modern phones do a screenshot and the image might be sized 800kb, 500kb. Even worse with screenvideo records. If you compress them on a basic website like this one: https://image.online-convert.com/convert-to-png a basic 700kb image can become easly 100-150kb without touching any extra setting and directly click convert, it comes out smaller, a lot smaller. So I suggest you to pick the fastest OFFLINE algorithm you can pick, and put that for the feature I described above.