Repository navigation
Image Resizing #1129
Closed
giliomeejg
started this conversation in
Ideas
Image Resizing
#1129
Replies: 4 comments
|
Totally on board with this @giliomeejg! cc: @thelostone-mc @nfrgosselin |
0 replies
|
Thank you for bringing the Pinata service to our attentiont, we will definitely use this. |
0 replies
|
Also investigate client-side image resizing before upload, as this will significantly reduce our costs during upload phase. |
0 replies
|
Closing this: we are now using pinata resizing + AWS CloudFront, and I believe this combination serves our needs perfectly. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The previous Alpha Round saw some pages loading with 100Mb of un-resized images.
This is detrimental to under served communities that fork out a fair bit of cash for bandwidth.
It appears that Pinata, which is already used, has an image resizing service that should be fairly easy to implement by simply adding '?img-width=200&img-height=100' to the end of the URLs being requested:
https://medium.com/pinata/resizing-ipfs-images-with-pinatas-image-optimization-tools-fb381bee58aa
As an example, here's an image that was loaded during the round, and resized on the client side to 296x120:
https://gitcoin.mypinata.cloud/ipfs/bafy...vchr2maura (3.9Mb)
Here's the same image, resized appropriately:
https://gitcoin.mypinata.cloud/ipfs/bafy...vchr2maura?img-width=296&img-height=120 (21Kb)
This is a 99.4% reduction in bandwidth and a relatively simple implementation.
All reactions