We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As simple as it sounds, Exnvr should allow for the option to compress a JPEG using a JPEG Compression approach before it's sent.
If this has to include a rate limit on # of images sent (like a max of 1 image per 20 seconds), so be it.
An interesting benchmark that we came across during the 360 compression research here
Billal suggests using
Interesting looking article https://fly.io/phoenix-files/resizing-images-using-elixir/
This will ofc mean adding a pipeline for intercepting images and pre-processing them rather than redirecting them.
@gBillal what do you think?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As simple as it sounds, Exnvr should allow for the option to compress a JPEG using a JPEG Compression approach before it's sent.
If this has to include a rate limit on # of images sent (like a max of 1 image per 20 seconds), so be it.
An interesting benchmark that we came across during the 360 compression research here
Billal suggests using
Interesting looking article https://fly.io/phoenix-files/resizing-images-using-elixir/
This will ofc mean adding a pipeline for intercepting images and pre-processing them rather than redirecting them.
@gBillal what do you think?
The text was updated successfully, but these errors were encountered: