If it’s not clear how to efficiently resize images client-side, we should probably resize them server-side after uploading.
Scenario
A user uploads an image 10MB. It’s checked against a [newly created] setting max_upload_image_size_kb.
The image is then resized to max_image_size_kb (for example, 3MB). So, no original image of 10MB is saved, but rather only the resized version 3MB.
A thumbnail is created for image if its size is bigger than max_image_width and max_image_height (the way it works now).
This way we allow users to upload big images without the boredom of resizing them before uploading. In the same time, we only store reasonable size of the images, configurable in Settings.
As far as I can tell, this rather large image that I’m using as a profile background is not resized in my profile pop-up. Every time I click my profile, it takes me well over a second to load the background. I’ve seen this in others’ profiles as well, and it’s quite jarring.
Even on my profile page, the background image ought to be optimised for screen size.
This would be REALLY helpful to my non-techie userbase.
Since we have limited storage on Digital Ocean, we can’t allow full size camera uploads anymore. I’ve imposed a strict 1MB limit to keep it under control (we have a LOT of photos). This means most people’s direct camera shots are too big, and must be downsized before posting.
Manually resizing all photos before uploading is annoying at best. To a less skilled user this can be frustratingly difficult, especially on mobile devices.
For us, bandwidth is not the immediate concern. I’d trade a lot of bandwidth for a simpler user experience.
