-
-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
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
Show original content #6638
Comments
Hey, I am ok with showing static images on landing (as a quick fix), however when user lands the page we should be able to load the dynamic one |
downside if we use IPFS gateway to show original content
so, it's better to show original content with our r2 bucket. then, need to assign our r2 bucket our public r2 domain |
Yup that is the plan from the new design |
How to differentiate between loading optimise image and non optimise images? sent additional queries to image-workers? for example |
PR for worker was merged and deployed on beta so its free to grab |
|
On it. or is it better to give this to new contributors instead? |
Yup ✅ |
👋 |
ASSIGNED - @justskinny5 🔒 LOCKED -> Wednesday, August 30th 2023, 24:10:26 UTC -> 36 hours |
@preschian @vikiival hi~ just want to make sure that the final solution is to show original content if the user clicks the preview button, right? |
Hello, The final solution is decribed in the Solution steps 1 and 2 |
Hi guys, currently, we show optimised images on the gallery detail page. The downside is that gif content will be transformed into a static image. For example, this page https://deploy-preview-6599--koda-canary.netlify.app/stmn/gallery/u-117-382
I'm using https://wsrv.nl/ to resize images on cf-workers. For now, that page still does not support resizing big-resolution gif to smaller-size gif.
Reason
To avoid loading "big" size images to the user. Because it will hurt performance and give them a bad experience on our website. Ref:
For example comparison, 17.8kB vs 2.2MB
Solution
wdyt? cc @kodadot/internal-dev
The text was updated successfully, but these errors were encountered: