skicomau
Active member
Hello everyone.
I have been running a forum for almost twenty years.
With the rise of sophisticated global social media the last six years (and obviously this means FB, Instagram, Twitter, Snapchat etc) - 1st class image management (uploading, optimising, serving) has become de rigueur -- especially if one expects your community to remain loyal and also to attract millennial members for whom a brilliant image experience is just a given.
To that end I am interested in what other forum operators have implemented to enable as frictionless an image experience as possible for their members.
Specifically...
Theme choice,
ie the graceful handling of responsiveness of images across devices including delivering for retina screens.
Lazyload techniques
best JS library
Image upload
Default XF flash uploader and fallback - or something else.
Image Optimisation
GDN/ImageMagick v's Add-ons that hand off file optimisation to coupled services such as Kraken, Optimus, Gifsicle etc.
Image storage for huge volumes of images
Local v's AWS v's offload to separate domain.
CDN v's Dynamic Image servers
eg maxcdn/cloudflare v's imgix/imagefly/cloudinary (cloudinary is expensive)
Linked images.
SSL solution, XF Proxy Images v's addon's like AndyB's Convert Image that prevent image link-rot.
My UX goals are the following;
1. Allow users to upload reasonably large images of 10MB with no image size (w x h) restrictions.
2. Upload with as little delay as possible (ie defer all processing)
3. Store the master image at original size - but after it has been file size optimised (ie manage my total disk storage overhead).
4. Desktop: Deliver version of image optimised for thread column width (905 pixels in my case) - if image is larger clicking images pulls in the master image at full size.
5. Mobile: deliver version of image optimised for device using srcset, provide 3 srcset choices. Tapping image in thread delivers best image for device (but does not deliver the master image if it is stupid large)
My stack to achieve all the above at the moment is;
-- UI.X theme (not current release)
-- Default XF uploader with Flash uploader enabled.
-- GFNio with Kraken.io as my Image Handler - not deferred.
-- [bd] Attachment Store using AWS buckets - deferred. Local Copy not kept - not using cloudflare (see next).
-- Imagefly as Dynamic image server for default desktop and mobile serving. (required editing template bb_code_tag_attach)
I have not yet got sorted for diferentiated retina experience.
I have not yet implemented a proxy/local solution for linked images.
I have not yet implemented lazy load.
My stack as described is still not ideal. Specifically GFNio and [bd] Attachment Store do not play nice and I am unable to set GFNio to deferred this means upload is 2x to 3x longer than necessary which is my primary gripe - plus I have not been unable to process with kracken the tens of thousands of legacy images that were already on AWS.
So....
If you have got to here and also consider Image Management one of the most important UX issues with running a great forum - please share your solution stack and experiences
thanks.
I have been running a forum for almost twenty years.
With the rise of sophisticated global social media the last six years (and obviously this means FB, Instagram, Twitter, Snapchat etc) - 1st class image management (uploading, optimising, serving) has become de rigueur -- especially if one expects your community to remain loyal and also to attract millennial members for whom a brilliant image experience is just a given.
To that end I am interested in what other forum operators have implemented to enable as frictionless an image experience as possible for their members.
Specifically...
Theme choice,
ie the graceful handling of responsiveness of images across devices including delivering for retina screens.
Lazyload techniques
best JS library
Image upload
Default XF flash uploader and fallback - or something else.
Image Optimisation
GDN/ImageMagick v's Add-ons that hand off file optimisation to coupled services such as Kraken, Optimus, Gifsicle etc.
Image storage for huge volumes of images
Local v's AWS v's offload to separate domain.
CDN v's Dynamic Image servers
eg maxcdn/cloudflare v's imgix/imagefly/cloudinary (cloudinary is expensive)
Linked images.
SSL solution, XF Proxy Images v's addon's like AndyB's Convert Image that prevent image link-rot.
My UX goals are the following;
1. Allow users to upload reasonably large images of 10MB with no image size (w x h) restrictions.
2. Upload with as little delay as possible (ie defer all processing)
3. Store the master image at original size - but after it has been file size optimised (ie manage my total disk storage overhead).
4. Desktop: Deliver version of image optimised for thread column width (905 pixels in my case) - if image is larger clicking images pulls in the master image at full size.
5. Mobile: deliver version of image optimised for device using srcset, provide 3 srcset choices. Tapping image in thread delivers best image for device (but does not deliver the master image if it is stupid large)
My stack to achieve all the above at the moment is;
-- UI.X theme (not current release)
-- Default XF uploader with Flash uploader enabled.
-- GFNio with Kraken.io as my Image Handler - not deferred.
-- [bd] Attachment Store using AWS buckets - deferred. Local Copy not kept - not using cloudflare (see next).
-- Imagefly as Dynamic image server for default desktop and mobile serving. (required editing template bb_code_tag_attach)
I have not yet got sorted for diferentiated retina experience.
I have not yet implemented a proxy/local solution for linked images.
I have not yet implemented lazy load.
My stack as described is still not ideal. Specifically GFNio and [bd] Attachment Store do not play nice and I am unable to set GFNio to deferred this means upload is 2x to 3x longer than necessary which is my primary gripe - plus I have not been unable to process with kracken the tens of thousands of legacy images that were already on AWS.
So....
If you have got to here and also consider Image Management one of the most important UX issues with running a great forum - please share your solution stack and experiences
thanks.
Last edited: