Open jongrim opened 1 year ago
I had a look at it and my understanding is that:
transform
option to download the picture in the target sizetransform
request, serve a size appropriate version of the pictureIt already looks pretty solid to me. Did you already take care of this, or were you talking about resizing / optimizing picture at upload time to save on storage costs?
Hey @BigEZ , this issue is a bit stale. I actually did end up implementing supabase's transform option, but then quickly discovered that the number of transforms that happen far exceeds the quota for the current tier.
I'm in a brainstorming / information gathering phase now as I think on what to do next. I've started a discussion to collect some feedback though I haven't had a chance to publicize it yet (I intend to make it more visible around end of the year I think). But it's clear supabase's transform option won't suffice. I've cut down it's usage to just avatars and community images and it's still over the limit, so I'm going to have to reduce it even further.
Is your feature request related to a problem? Please describe. The images uploaded are not optimized for web
Describe the solution you'd like Images should be optimized to minimize data costs
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.