The segment immediately after the hostname is the signed part, which is generated based on all the other parameters (ie quality, dimensions, crop coordinates and source image url). If you change any part of the URL, the server will return a 404. There's no way of providing a set of client-side rules for how to generate the URLs for the different size images, without leaking our secret key. An option would be for the entire URL to be the configuration, but then all you've achieved is moving the config out of data attributes and into javascript config objects.
/https://ofs-media-production.s3.amazonaws.com/media-library/be3c3d92397a3a2af72662c1838885163c48c12f.jpg){kind=link}
http://cropper.onefinestay.com/s3NY9Z5QncGSnphA8QhOStz36wQ=/...
The segment immediately after the hostname is the signed part, which is generated based on all the other parameters (ie quality, dimensions, crop coordinates and source image url). If you change any part of the URL, the server will return a 404. There's no way of providing a set of client-side rules for how to generate the URLs for the different size images, without leaking our secret key. An option would be for the entire URL to be the configuration, but then all you've achieved is moving the config out of data attributes and into javascript config objects.
Essentially, this is what we're doing: https://gist.github.com/AndrewIngram/7871392