11–20 of 22 posts
On my gallery page:
> By upgrading your image server to thumbor you would go from 16687.68kb to 29581.33kb for 19 images (using WebP images).
All of my images get filtered through convert through convert(1) -quality 90, could that be a reason?
Dealing with on-demand thumbnails is annoying, I've done something similar in the past [1]. In any case, transparently generating thumbnails from URLs is the saner solution, designers/editors might want to embed image of all sorts of sizes and aspect ratios and you can't always generate everything in batch - this is extremely common on news sites. [1] https://github.com/hcarvalhoalves/django-rest-thumbnails
Dealing with on-demand thumbnails is annoying, I've done something similar in the past [1]. In any case, transparently generating thumbnails from URLs is the saner solution, designers/editors might want to embed image of all sorts of sizes and aspect ratios and you can't always generate everything in batch - this is extremely common on news sites. [1] https://github.com/hcarvalhoalves/django-rest-thumbnails
Anybody know of a rails equivalent?
That said, it usually feels safer to have something that works with the same stack.
We're using carrierwave, and it's pretty neat, but we had a few times where we had to scale thumbnails differently, and it turned out to be a pretty long batch operation, especially since we're storing images on S3.
I think that 'on-the-fly' conversion and caching could work better for larger sites that tend to change. Pre-processing doesn't scale so well.
[0] take a look at https://github.com/rafaelcaricio/thumbor_rails, which I believe is using https://github.com/thumbor/ruby-thumbor
EDIT: added links
> By upgrading your image server to thumbor you would go from 0kb to 0kb for 0 images, thus saving NaN% (using WebP images).
Maybe a special message could be used in this specific case.
A similar app I worked on, which focuses on extensibility: http://magickly.afeld.me/
> By upgrading your image server to thumbor you would go from 12989.07kb to 16106.04kb for 22 images (using WebP images). On my gallery page: > By upgrading your image server to thumbor you would go from 16687.68kb to 29581.33kb for 19 images (using WebP images). All of my images get filtered through convert through convert(1) -quality 90, could that be a reason?
Nice work! > By upgrading your image server to thumbor you would go from 0kb to 0kb for 0 images, thus saving NaN% (using WebP images). Maybe a special message could be used in this specific case.
on firefox maybe you should display a dummy webp image. Seems like FF doesn't support it yet, you should degrade gracefully in this case.
Just saw it. You are absolutely right. My bad... Will fix it tomorrow.
Now the strange thing: thumbor requires cookies in order to serve images. It requires quite lax settings since allowing cookies for thumborg.org as first party only doesn't suffice. I need to accept all possible cookies, I think because one offending cookie has domain .thumborg.org.
I think serving images should not depend on cookies, or is there a good reason?
A similar app I worked on, which focuses on extensibility: http://magickly.afeld.me/
Not sure how it compares, but thumbor is fully extensible. There are people using it with HBase, others with Amazon's S3 and Cloudfront, others with filesystem based solutions and yet others with redis or mongo backed images. Other than storage, you can extend loading images from different places, as well as changing the imaging library thumbor uses. You can also extend the filters or the detection mechanisms. Anyway…
For example, we have a ruby-based library for converting images for different types of colour-blindness[0]. It's available from ruby, or via the command line. How could we use it as a filter in thumbor?