Enabling Image Downsizing by Default

Unknown
Unknown
edited July 2019 in Product

Hi all, we have a request from ops to downsize upload images by default, rather than make it an opt-in feature. This would save bandwidth and probably make for a better user experience. However, it would be a change that customers would then have to go turn off if they wanted to revert.

Can I get an idea from CSMs & support as to whether doing this in the next product update would cause a disruption to our existing customers?

Feature Request

https://github.com/vanilla/vanilla/issues/9048

Feature Docs

Look for "Image Upload Limits" in our release notes.

Comments

  • Unknown
    Unknown
    edited July 2019

    Alternate complementary solution:

    I'm going to add my grain of salt here.


    I don't think that turning the feature ON by default will solve the problem on Ops side.


    Currently we have one client taking 1/3rd of our total traffic. Having that client turn off the feature (because they can) will cause the same issue again.


    Furthermore it will be hard to come up with a size that makes sense for everyone. Doing it on a per client basis would be a nightmare.

    What would likely be a better solution would be to create a thumbnail of the big images and display that on the posts. If you click on the thumbnail you open the real image in a different window.

    By doing so, opening a discussion with big images would not be so costly bandwidth wise and it would allow users to see the full resolution images if they are really interested in doing so.


    Optionally, as an example, we could say that 2500X2500 pixel is the limit (6.25Mpixel) size we allow for upload on our platform. This would ALWAYS be enforced not matter what. This would help to cut the number of edge cases (images of multiple MBs)

Categories