Yes. Sometimes thumborize.me will get the image sizes weirdly. It's there mainly to give you an idea. The settings are the standard ones that come with thumbor. If you tinker with the settings you always get best results. I highly encourage you to try it on your site with different quality settings. Setting up thumbor in your machine takes like 2 minutes. Have a look at the getting started page. If you need any further help please do not hesitate to create an issue and we'll most definitely help you.
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, good to know about magickly.
any tips on plugging-in any 3rd party image processing filters? Maybe I looked in the wrong place, but could only see storage plugins on the wiki.
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?
It can be easily implemented as a filter[1][2]. If you need to use it via command-line you can save the current buffer as a tempfile[3], call your CLI with the tempfile path and read the tempfile to use as the new buffer.
It's even simpler if your CLI can take a stdin argument, since you can just pass the buffer as a stdin parameter.
Thumbor's filter infrastructure allows you to change the image incrementally.
I don't load them via javascript, but I have an onError handler where I replace images with icons if they don't show up. The site is https://lifeprotips.com
Some people might downvote me for this (as happened before) but I have cookies disabled by default. Only if I need to interact with a website I am ok with traces and I allow cookies for that domain via the Cookie Controller add-on.
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?
At globo.com we have near a billion images (we are a big portal). Can you imagine pre-generating that many images every time a new format gets added?
We serve everything with thumbor with a Varnish cache in front of it and we're very happy with it. It has enabled our designers to work with any image size they can think of.
We use Thumbor at Yipit, and we are very happy with it. One thing that was not mentioned was extensibility... With thumbor it's easy to create new plugins and filters to extend your installation set of features.
Definitely... We get around 50M page views/day in our website. And since we are a media company we need to have a storage of images from celebrities, sports and news in general.
I agree, but one of the next features we'll implement is for you to be able to write stream processors, mappers and reducers in any language you want. Stay tuned!