[Feature Request] Cache Icons Locally

[My-Random-Thoughts]

Description

Instead of relying on cdn.jsdelivr.net for grabbing/loading icons every time the page loads, how about caching them for faster transfers. This would also help in the case of temporary internet loss.

Other

No response

[benphelps]

Your browser should be caching these resources, that's none of the business of homepage.

[My-Random-Thoughts]

I agree to some extent, but if I go to my page during an internet outage, I am left with lots of "logo" images.
My thought was that if there was a cache folder (or whatever) that logos were downloaded to, it would help in those situations.

[benphelps]

It's hard to justify the complexity of caching when you could just grab them and serve them locally all of the time.

[brunic]

The instructions only have how to config icons locally with containers. If without docker, how should I use the icons locally?

[benphelps]

Just place the files in the public folder.

[nomandera]

I landed here for the same reason.

Within the last few days my internet went offline. During this time all my intranet services lost icons. This was not the end of the world but it was really unexpected.

Can I suggest that rather than everyone rolling their own solution to grab them and serve them locally all of the time. we include a simple non blocking startup option that refreshes the local store.

Telemetry

On a related topic I found myself reading the jsdelivr privacy policy and AUP and whilst they are fair they do essentially allow for any legal organization to request personal information.

On top of this because of their peering all the following polices and in turn their peering and linked policies also apply

• Cloudflare https://www.cloudflare.com/security-policy/
• Fastly https://www.fastly.com/privacy
• Gcore https://gcore.com/legal
• Bunny https://bunny.net/privacy

In a world where all data is mined if allowed by policies we can be certain Homepage usage is being harvested and sold by one of these companies.

Given the self hosted community is quite sensitive to this I would suggest the effort to allow for essentially opting out of telemetry by local caching as suggest above be of higher importance that the purely technical gains it would bring.

[benphelps]

Bluntly, no.

This is entirely up to the end user to decide where they want their icons served from, and we offer a myriad of options already. Caching locally would be complex and lead to more issues than it would solve (imagine the number of issues now for "i updated my icon and it's not changing").