Subtle changes, bugs and feedback

You are reading a single comment by @gbj_tester and its replies. Click here to read the full conversation.

•

Velocio
Well... I reckon it's probably reasonable to do this:
1. Configure nginx to accept 64MB or smaller
2. Configure the API to accept max dimension of 1920 px high or wide
3. Configure the API to accept max resolution of 132 dpi
4. If either the max dimension or the max resolution is exceeded then reduce to fit a 1920 box (but preserve aspect ratio) and reduce to 132 dpi
5. If either the image dimensions or dpi cannot be determined, then this is not a valid image and reject
On #5 this does mean that some PNG images may be rejected even though they are valid files. i.e. animated PNGs that use different colour palettes per frame.

•

gbj_tester in reply to @Velocio

Configure the API to accept max dimension of 1920 px

This is OK up to a point, but sometimes it's useful to be able to see images at original scale to zoom in on details, particularly in current projects if something looks awry and the builder doesn't seem to have caught it. I've been encouraging people to use the lfgss upload because all the other free image hosts suck so hard for various reasons and most people CBA to provide their own server.

•

Velocio in reply to @gbj_tester

Hmm.

Good point... let me go and check the cost of hosting images at the moment.

Maybe I should just up the file size? Super simple to do... just a question of cost.

About

Avatar for gbj_tester @gbj_tester started