111–120 of 152 posts
> No way to retrieve original image that's probably the logical continuation of video hosting - if you upload something to, say, YouTube, you also don't expect to be able to retrieve the original video from there. It may be a high-quality version, but it still gets reencoded on upload...
For anyone looking for an alternative, https://imgproxy.net/ works v. well.
Earlier quoted context omitted.
I want to maintain the aspect ratio of my crop, not that of the source image. Perhaps `fit=cover-scale-down` would be a more appropriate name. In other words, I always want a square image <= 512px wide. I think this is a very common use case.
If there's no way to specify where the center (or w/e) of your crop is on the source image, it's not going to happen.
Is there an image (or video) service that does: * You bring your own storage * You bring your own CDN For instance, you configure your CloudFront distribution to source from the Image Transformation service. You configure your Image Transformation service to source from your S3 bucket. This seems like the best of all worlds to me. Does this exist?
Disclaimer: I work for the company
Is there an image (or video) service that does: * You bring your own storage * You bring your own CDN For instance, you configure your CloudFront distribution to source from the Image Transformation service. You configure your Image Transformation service to source from your S3 bucket. This seems like the best of all worlds to me. Does this exist?
Yes, that's totally the description of Transloadit https://transloadit.com/ You import from your own storage and export wherever you want also, we handle the encoding and transformation for you. We don't support CloudFront yet, but we support export/import from S3 and a lot of other providers. Disclaimer: I work for the company
Thanks for the feedback. I'm on the CF Images product team. We will allow the download of the original images, it is actually one of the next features coming up. Also we will introduce webhooks and Images Analytics next.
Approximate date in images is a huge issue. There's a range of ways to express uncertainty to date, not after. not before. circa. between. year good month uncertain. If you invested in this space, you could help simplify the thinking. Ramming it into specific YYYY:MM:DD:HH:MM:SS values is really bad.
Google is a bad actor here in photos: they don't re-index on tag modification except for very specific changes and its opaque and poorly documented. If you do better it has good qualities about market and mind share.
Earlier quoted context omitted.
I assure you it's not just you. I see it from the other end as well. Not long ago I had a client shout "I don't want to hear about your roadmap!" and grab his team and walk out of a meeting. We really shouldn't have used that terminology there, since the feature they needed was actually already in beta test with a few friendlies, we could have added them to the beta test cohort on the spot, and demonstrated it in the…
I can empathize with the customer here. I have also seen it from the other end, working for a large and slow SAAS organization. I see PMs always wanting to show the customer the "roadmap" because they think it somehow appeases the customer and calms their wrath. The wiser customers know that a roadmap is not a promise, and will take it with a huge grain of salt. I have grown to almost despise the word or mention of i…
When I first saw this product announced, I immediately wanted to replace my manual solution with it. I’ve been putting it off because other work had to be done, but now that I read this, I think I’ll stick with my current workflow for now. What I’ve been doing is first resize an image to multiple specific sizes using Vips ( https://www.libvips.org/API/current/using-cli.html ) for size in 8120 5260 3840 2560 1920 1200…
We were charged $10k for the first month of use and immediately reverted the implementation. CF was kind enough to refund us since we're still an early stage co. It would be great if pricing was more reasonable
The website itself was already using cloudflare's CDN. So I added a simple cloudflare URL rule to redirect all requests hitting /images/XXX to the 3rd party image hosting service. Within a month our client's image hosting bill dropped from $~10k/month down to about $90/month, which I felt great about.
I did made one terrible mistake though - I forgot to tell our client about the configuration change. So cue a monday morning panicked phone call from our client when they got their bill, asking what on earth was happening that caused all their web traffic to disappear overnight. They thought (based on the bill) that their website must be broken and they were freaking out about it! Oops!