Pixboost news and updates. February review
We were lucky to catch a big fish. We just finished integration on a big enterprise client. I will definitely write a detailed Use Case in a next post about it and how we did it. Therefore, February was pretty fun and hectic.
It is such a great feeling when the amount of requests to your service is going up exponentially and the service stays nice and stable.
What a joy when you can say “well done” to the team and “Cheers” when having a small celebration.
Let’s cut it short. We delivered some valuable features directly to the enterprise customer. Below I’ll summarize what is available now.
The New Quality Calculation Algorithm
We changed slightly optimization algorithm for JPEG images.
Before we were checking quality on the original image and if it’s above 82 then we set it to 82 for an optimized image. If quality was already below 82 then we didn’t change it.
During tests, we have found out that designers usually set the quality to the desired value and they are not keen to lower it to 82.
It makes sense actually, so, a new algorithm is checking if quality of the original image is 100 then it will set to 82, otherwise just leave it at original value.
So, if we need to optimize a photo from a camera that hasn’t been optimized then we will do additional compression, but if it’s a designer who created a banner and exported it with the quality of 92 then we’ll keep it at 92.
If you are interested in the code then you can look it up here on github.
Support of the URLs without protocol
In the HTML you can reference image without protocol like that:
<img src=”//mysite.com/logo.png”/>
Pixboost now supports this reference in the URL:
<img src=”https://pixboost/api/2/img///mysite.com/logo.png/optimize”/>
In the example above https will be used to fetch the image. You can use http as well just by changing a protocol in the prefix:
<img src=”http://pixboost/api/2/img///mysite.com/logo.png/optimize”/>
Even more, you can omit protocol completely and it will use the protocol from the browser:
<img src=”//pixboost/api/2/img///mysite.com/logo.png/optimize”/>
You can see this change here on github.
Allowing requests from sub-domains
Sometimes it is useful to allow image transformations from all sub-domains. Until now there was no way to do this. You had to add all sub-domains directly. For instance, like on the picture below:
Now, you can add all sub-domains just by prefix domain with . (dot):
Stay tuned!
We have many new features in progress. Most of them are relating to the integration. You can see some of them on github. We are planning to release them next month.
