My News feed just broke because I couldn't load images that had been uploaded from user phones.
I just came across an issue while trying to load my site after a few big images had been uploaded from user phones. I posted about this a while back on Community Builder and it took them a while but eventually they fixed the problem.
https://www.joomlapolis.com/blog/kyle/18703-client-side-image-resizing
Here's a summary of my post:
To get users using online communities (other than the major players), they need to be able to load pics quickly and easily. If they take a photo on an iphone, and it can't be uploaded because the image is too large (ie. greater than the upload limit) or it takes 30-60 seconds to upload, they'll stick to sharing on Facebook or Instagram as it's much easier.
In the past, users would upload the pic from their SD card, resize and compress, then upload, but very few users do this or use a phone app to shrink an image nowadays. People assume the site or app will do the shrinking and if they've got the choice of:
a) taking a photo, opening it in an app (or downloading one), choosing what size to save it as, resizing then compressing, then saving, then going back to the CB site, opening and then sharing
versus
b) taking a photo, uploading it using on-the-fly compression/resizing
...any given sane user will choose (b).
Facebook, Instagram and Whatsapp use on-the-fly compression using an algorithm like
this or this via mobiles.
....
Making ES mobile ready and integrating on-the-fly compression/resizing should be a priority. It seems that suitable code exists such as plupload or JIC .
CB Response:
Client side resizing and thumbnail cropping is already planned. It wasn't reliably supported until HTML5 officially launched (using canvas elements) and wasn't widely available until just recently due to browser support so it couldn't be implemented until that point. Facebook probably uses this technology now, but it absolutely did not before. I wager they still have a fallback of some sort as the only way to do client side resizing before HTML5 was through Flash or Java applet. My point is it's extremely new still.
The client side resizing will likely just become a part of our validation code and be done entirely silently based off the image fields settings. I've added a feature ticket to keep track of the client size resizing, but it's unlikely to make it into CB 2.1.
I just came across an issue while trying to load my site after a few big images had been uploaded from user phones. I posted about this a while back on Community Builder and it took them a while but eventually they fixed the problem.
https://www.joomlapolis.com/blog/kyle/18703-client-side-image-resizing
Here's a summary of my post:
To get users using online communities (other than the major players), they need to be able to load pics quickly and easily. If they take a photo on an iphone, and it can't be uploaded because the image is too large (ie. greater than the upload limit) or it takes 30-60 seconds to upload, they'll stick to sharing on Facebook or Instagram as it's much easier.
In the past, users would upload the pic from their SD card, resize and compress, then upload, but very few users do this or use a phone app to shrink an image nowadays. People assume the site or app will do the shrinking and if they've got the choice of:
a) taking a photo, opening it in an app (or downloading one), choosing what size to save it as, resizing then compressing, then saving, then going back to the CB site, opening and then sharing
versus
b) taking a photo, uploading it using on-the-fly compression/resizing
...any given sane user will choose (b).
Facebook, Instagram and Whatsapp use on-the-fly compression using an algorithm like
this or this via mobiles.
....
Making ES mobile ready and integrating on-the-fly compression/resizing should be a priority. It seems that suitable code exists such as plupload or JIC .
CB Response:
Client side resizing and thumbnail cropping is already planned. It wasn't reliably supported until HTML5 officially launched (using canvas elements) and wasn't widely available until just recently due to browser support so it couldn't be implemented until that point. Facebook probably uses this technology now, but it absolutely did not before. I wager they still have a fallback of some sort as the only way to do client side resizing before HTML5 was through Flash or Java applet. My point is it's extremely new still.
The client side resizing will likely just become a part of our validation code and be done entirely silently based off the image fields settings. I've added a feature ticket to keep track of the client size resizing, but it's unlikely to make it into CB 2.1.