Bugs Fixed Images not loading often?

[JreeX]

Is it just me or are images not loading often? Just appearing with blue “?”

Swapped DNS to cloudflare and turned off all protection on the router level. Still the same thing.

 

[ikeo1]

Is it just me or are images not loading often? Just appearing with blue “?”

Swapped DNS to cloudflare and turned off all protection on the router level. Still the same thing.

I don’t see this issue… what browser are you using? Are you using ad blockers? Images are served from a different location we also use webp format which is higher efficiency but has some compatibility problems with older browsers/phones

I don’t see any errors. Can you take a screenshot too?

 

[JreeX]

Here

Using safari and brave.

 

[ikeo1]

Sent a DM

 

[GoldensRule]

Here

Using safari and brave.

Which version of iOS are you running? You need at least version 14 for webp to render reliably.

 

[JreeX]

Which version of iOS are you running? You need at least version 14 for webp to render reliably.

Latest 26.3.

Also run into this a lot. Might be the browser.

 

[GoldensRule]

Latest 26.3.

Also run into this a lot. Might be the browser.

I would try clearing your iphone cache, see: https://support.apple.com/guide/iphone/clear-your-cache-and-cookies-iphacc5f0202/ios

 

[command_liner]

I don’t see this issue… what browser are you using? Are you using ad blockers? Images are served from a different location we also use webp format which is higher efficiency but has some compatibility problems with older browsers/phones

I don’t see any errors. Can you take a screenshot too?

Webp is a general purpose image compression tool. It has better compression than JPEG, but has all of the errors of JPEG.
That is to say, for high-contrast image data, JPEG and webp, by default, introduce error into the compressed data stream,
and are not particularly good compression engines. Yes, you can configure webp compression to be lossless, and have high
compression, and can even configure the thread count used for compression. Calling webp "efficient" is like calling a car
"blue" -- it may be a true statement, but the statement has no particular meaning.

Contrast webp to zstd. The latter was designed to be run on Intel-like machines with a minimum of branches and context
switches. The compression ratio is very high, but the expense of compression is borne by the compression system. Uncompression
is almost free -- very quick. Web service providers push the cost of decompression to the end user by using webp. It is
just a business decision.

The webp decompression in safari is known to be faulty. Just like the zstd compression done by Cloudflare was defective
for almost a year. Yes, I spotted that one. The task of writing thread-safe compression using a variable number of threads
is REALLY HARD. AFIAK, I wrote the first correct thread-safe version of zlib, and there were 22 separate boundary conditions
for threads and buffers. That was a long time ago, but the general problem is still difficult.

It is not clear what configuration of webp is used herein: some configurations are going to interact with some buffer sizes and
thread counts worse than others. You can look the problem up elsewhere.

I am on Mac now... not using Safari because the webp lib is defective.

 

[22plinker]

Latest 26.3.

Also run into this a lot. Might be the browser.

I have been getting this same error quite a bit lately as well and have never seen it before. (just in the last several days) I'm on a home computer using Chrome and have updated but still getting the error.

Matt

 

[JreeX]

Good to know maybe it’s not just me

 

[ikeo1]

I put in a fix for this. Let me know if it improved for you guys. This should specifically help firefox/brave.. I think I also resolved the issue with Avatars | Banners.. That was an annoying bug