Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Issues with Cloudflare Images

blog.klungo.no

Post reply on HN
Print view View original

141–150 of 152 posts

Re: Issues with Cloudflare Images

#141

Post by yawnxyz »

jjkmk wrote: post #88
yawnxyz wrote: post #18

Earlier quoted context omitted.

I remember there was another article about image uploads and content moderation (here: https://news.ycombinator.com/item?id=28684250 ), essentially saying that if you create a open uploading service, you WILL start getting lots of spammy images / abuse. CF Images always seems like a LOT more $$ than other image hosting tools out there. What other service did you end up going with?

How does imgur stay alive, out of curiosity.

they also removed the private images part, and pivoted towards becoming a "social network" (several years too late). Honestly no idea how they stay alive.

Also honestly no idea why they never jumped on the NFT bandwagon.

Oh, they're also apparently a tiny team (<50) too, so that probably helps

Re: Issues with Cloudflare Images

#142

Post by manigandham »

AtNightWeCode wrote: post #11

"5. Lack of dynamic resizing, only 20 “variants” allowed" Best practice when it comes to images on the web is to use a fixed number of sizes. Why they limited it to 20 I do not know though. You should never allow dynamic image resizing since it is commonly used in various attacks.

All major file/image upload services use signed URLs to prevent this. It's a minor abuse vector and not much of an issue.

Cloudflare started as DDOS protection and should add similar features rather than limit functionality.

Re: Issues with Cloudflare Images

#143

Post by sciurus »

josephg wrote: post #120
jcsnv wrote: post #10

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

I had a client a few years ago who was using another service for image hosting, and they were getting charged through the nose for it. This is before cloudflare had their own image CDN style service. The client's app made heavy use of URL based image transforms. And we didn't want to lose that - so it seemed like they were a little stuck. The website itself was already using cloudflare's CDN. So I added a simple clou…

Your post leaves it a little bit unclear what you actually did.

Are you saying that

1. Originally all requests for images went directly to the egregiously-priced image host

2. You changed that traffic to be routed through Cloudflare instead so it would be cached

3. That reduced requests to your image host enough to cut your bill by 99%

?

Re: Issues with Cloudflare Images

#144

Post by dewey »

imglorp wrote: post #105
carom wrote: post #6

I've run into a lot of these issues using it and I've even reported them on every available channel. The original image is my biggest complaint. I was making a service where users would want to batch retrieve what they've uploaded. No response on the forums to that. Also hit the CORS issue, so rather than fetching an image and loading it into a canvas I have to use a fake image element. This makes the canvas untruste…

Maybe I'm dense, but what's the usecase of downloading an original image from CDN? You upload it to distribute widely, and then lose it?

"Images is a single product that stores, resizes, optimizes and serves images"

Because it's not just a CDN but does many more things. With this product description (taken from CF blog post) I'd expect it to behave like a storage bucket containing the files (including the raw file), with an image resizer and CDN attached.

Re: Issues with Cloudflare Images

#145

Post by ranrub »

youngtaff wrote: post #135
tgtweak wrote: post #83

Cloudinary is really a frontrunner in this. Cloudflare should have bought them out vs try to build something that they clearly aren't equipped to do.

CDN's should eat most of Cloudinary's market… Cloudinary has two parts - a Digital Asset Manager for storing content - an service for optimising / resising images (and video) that then uses Cloudflare, Fastly etc as a CDN Akamai, Cloudflare, Fastly all already have image optimisation services, so if you're using them already why use Cloudinary. The DAM piece is more of an issue as most CMSs aren't great on the asset…

Cloudinary is an end-to-end solution for managing images and videos, for developers. The CDN and optimization parts are tightly coupled with the digital asset management: e.g. if you change an image, the system knows to invalidate the relevance cached images, and is CDN-agnostic. So no, CDNs are not competition, but rather good partners to Cloudinary.

Regarding the DAM: CMS and Ecom systems are indeed getting better, but media assets you upload to them become siloed in the CMS. Cloudinary acts as a headless DAM that you can embed in any CMS and use as a single source of truth, relieving a lot of the pains of handling media files and their versions.

FD: I'm a Cloudinary employee

Re: Issues with Cloudflare Images

#147

Post by youngtaff »

ranrub wrote: post #145
youngtaff wrote: post #135

Earlier quoted context omitted.

CDN's should eat most of Cloudinary's market… Cloudinary has two parts - a Digital Asset Manager for storing content - an service for optimising / resising images (and video) that then uses Cloudflare, Fastly etc as a CDN Akamai, Cloudflare, Fastly all already have image optimisation services, so if you're using them already why use Cloudinary. The DAM piece is more of an issue as most CMSs aren't great on the asset…

Cloudinary is an end-to-end solution for managing images and videos, for developers. The CDN and optimization parts are tightly coupled with the digital asset management: e.g. if you change an image, the system knows to invalidate the relevance cached images, and is CDN-agnostic. So no, CDNs are not competition, but rather good partners to Cloudinary. Regarding the DAM: CMS and Ecom systems are indeed getting better,…

Yeh, I'm well aware of what Cloudinary does and I've used it with clients.

I've also used CDNs and CMSs to achieve the same thing including invalidating images in CDN caches when they change

Given the choice I'd always go for a solution that uses one of the good three CDNs combined with a CMS that can invalidated edge content

Re: Issues with Cloudflare Images

#148

Post by tgtweak »

youngtaff wrote: post #135
tgtweak wrote: post #83

Cloudinary is really a frontrunner in this. Cloudflare should have bought them out vs try to build something that they clearly aren't equipped to do.

CDN's should eat most of Cloudinary's market… Cloudinary has two parts - a Digital Asset Manager for storing content - an service for optimising / resising images (and video) that then uses Cloudflare, Fastly etc as a CDN Akamai, Cloudflare, Fastly all already have image optimisation services, so if you're using them already why use Cloudinary. The DAM piece is more of an issue as most CMSs aren't great on the asset…

Cloudinary does a lot more than asset management, the depth of at-request-time functionality you can get just by URL params alone (like cropping with face detection...) is untouched by any of the cdn offerings of "let me resize/compress that for you".

The only thing that is shitty about the cloudinary model is the bandwidth costs. If someone could combine the functionality of cloudinary (it is genuinely unmatched in the space) with the cost of cloudflare... I'm in. They're even doing a great job on video editing (changing encoding format, bitrate, container, splicing in audio, cropping, thumbnail...) again using the same "just change the url and it's done" approach.

Saying CDNS will eat this by offering mediocre asset management is not apt.

Re: Issues with Cloudflare Images

#149

Post by josephg »

sciurus wrote: post #143
josephg wrote: post #120

Earlier quoted context omitted.

I had a client a few years ago who was using another service for image hosting, and they were getting charged through the nose for it. This is before cloudflare had their own image CDN style service. The client's app made heavy use of URL based image transforms. And we didn't want to lose that - so it seemed like they were a little stuck. The website itself was already using cloudflare's CDN. So I added a simple clou…

Your post leaves it a little bit unclear what you actually did. Are you saying that 1. Originally all requests for images went directly to the egregiously-priced image host 2. You changed that traffic to be routed through Cloudflare instead so it would be cached 3. That reduced requests to your image host enough to cut your bill by 99% ?

The client was using an image host which supported image transforms. They uploaded all their images there and were using a lot of image transforms from that host on their website. So, HOST/img/123?scale=1.3&color=greyscale type business. They were paying per image loaded from the site.

We tucked cloudflare in front of the image host using a URL rewrite rule. Cloudflare's cache reduced the number of requests made to the image host by 99% or something.

Re: Issues with Cloudflare Images

#150

Post by top_kekeroni_m8 »

Slartie wrote: post #95
leenyburger wrote: post #55

I thought Cloudflare was going to win the image hosting/serving/resizing game based on their original blog post, but that doesn't seem to be the case. I kept getting frustrated with the complexity and changing costs of solutions out there, so about a year ago I launched https://www.simplefileupload.com . It's a super easy, flat rate cost solution to quickly allow users to upload images and files. It provides a custom…

Isn't it a bit too easy to exploit this? Like by maliciously uploading tons of data to the account of a site using this service in order to exceed their limit and hence break their file upload process.

There is no free plan.
Post reply on HN