Why some images aren't automatically downloaded?

(Fábio Machado De Oliveira) #1

For some images, I notice Discourse downloads a local copy. It doesn’t happen for some of them.
I observed in the same image from this Lightboxed images with giant filenames cause horizontal scroll

Its in google cdn:

(Jeff Atwood) #2

What if the image is 3 gb? Should it be downloaded? That is one reason.

(Fábio Machado De Oliveira) #3

How does the setting “Retrieve images from remote URLs to insert the correct width and height dimensions” works? What triggers it?

I saw Discourse did it for some other image, and now I’m not sure what is the expected behavior. Is it the image size?

(Kane York) #4

That’s automatically done for all posts after you submit it.

The “download remote images to local” setting is probably what you’re thinking about. It turns off automatically when there is less than 25% disk space left, and the admin must manually turn it back on (and change the % or free up disk space).

(Régis Hanol) #5

I kinda replied here

The image you linked is a WebP file. Since it’s only supported by Chrome right now, we don’t even consider it an image.

(Fábio Machado De Oliveira) #6

After you mentioned it in the previous topic, I figured the playstore links a different format depending of the browser you’re on. I think I’m using the firefox version, and maybe its the lack of a extension in the filename.

(Régis Hanol) #7

Yeah, that too :slight_smile: We need the extension to be able to recognize it is an image.

(Fábio Machado De Oliveira) #8

It’s good enough for me, I was not sure about the disk space tradeoff in my specific case.