We are regularly working on the problem with the servers. Unfortunately, Server 1 is no longer available for use, we are replacing it with an alternative. Server 2 was introduced as an alternative, it is stable and fast. At the moment there is a limit of 300 optimizations per day, but we will increase this limit, now we are testing the server for fault tolerance. The plugin is developing and this is only a temporary problem that suddenly appeared.
@sardelich Allow me to elaborate on “the problem with the servers” that they’re “working on regularly.” 🙂
- Both WP Optimize and Robin Image Optimizer offer free image optimization, but not with their own infrastructure – they rely on reSmush.it infrastructure.
- WP Optimize was kind enough to officially acknowledge this in their plugin and also support reSmush.it by paying a monthly fee for commercial use. Thank you!
- Robin Image Optimizer not only fails to officially acknowledge that they have been using reSmush.it servers to power the commercial use of their plugin, but they also refused to contribute a small monthly fee to support reSmush.it’s costs. In our communication with them, they explicitly agreed to stop using reSmush.it infrastructure to power Robin Image Optimizer.
- For almost a month now, we have been limiting access to reSmush.it servers for Robin, but they continue to push updates attempting to circumvent these restrictions. This is the actual reason for the “problems” and their “solutions.”
It would be nice if the Robin team acknowledged that they have been piggybacking on reSmush.it’s infrastructure from the very beginning, stopped attempting to do so, and started using their own servers.
@resmushit
The plugin description stated that the free server uses the resmush.it infrastructure, and we had agreements with the previous owners of the service.
We also did not refuse to pay you a monthly fee, since you became the new owners of the resmush.it service. However, you regularly increase the cost of the server, although the number of requests to your servers only decreases.
We paid you for using the server until January 9, after our refusal, you sharply limited access, not taking into account that we had not yet had time to deploy a new server.
Your goal was to harm Robin users, it was not very friendly, despite the fact that we complied with our agreements with you.
And in order to spend the New Year holidays with my family, I worked on solving the problems with the servers. Bravo ShortPixel, an excellent solution to get rid of competitors!
Since version 1.8.3, your server is no longer in use.
Dear @alexkovalevv
I wanted to take a moment to clarify a few points regarding our collaboration:
- We only increased the API price once after a year of your usage, and this was done solely to keep up with inflation and operational costs.
- Our intention has never been to harm your users. On the contrary, we agreed to offer you access to the API for an extended period, even though we had no direct benefit from doing so 🙂
- Unfortunately, it was your actions that ultimately impacted your users. Instead of reaching out to find a solution, you chose to push updates to your plugin that attempted to circumvent our API restrictions.
- I first reached out to you in early November, providing ample time to respond and work toward an agreement. However, it seemed this matter wasn’t prioritized on your end.
Good luck with your plugin in the future, and thank you for no longer attempting to bypass the proper use of the reSmush.it infrastructure.
Well…..first of all I love RIO and how its simple and effective. From that side, respect to the developers. Second, I, of course will not comment on any agreement between the developer and the server owners, I am just happy that my post started an open and public discussion between the sides involved.
I would also like to clarify a couple of points.
Yes, the price was increased once, but by two times. Please do not tell fairy tales that you were trying to compensate for the costs. We are well aware of the load our users created on your infrastructure.
You announced the price, it seemed fair to us and we paid regularly. But you decided to double the price, from the beginning of 2025 and notified us about it.
Since our subscription was paid until January 8, we decided to switch to our own server at the beginning of the year. I am not sure that we should have told you about our plans in advance. The subscription was paid and we did not plan to renew it, which I informed you about 10 days before it expired.
Instead of accepting this news with dignity and ending our relationship in a civilized manner, after the end of the paid subscription, on the same day, you turned off your infrastructure, returning the payment for December. You did this intentionally, so that we would experience difficulties. Instead of smoothly transferring users to our infrastructure, we were forced to look for a way out. We found it.
Server 2 yet giving “Error: Server responded an HTTP error 429” at all images…
