- cross-posted to:
- lemmy_admin@lemmy.ml
- cross-posted to:
- lemmy_admin@lemmy.ml
I was getting close to hitting the end of my free object storage so there was time pressure involved haha.
Seems to work but I haven’t tested it too much. Currently running on my instance.
That’s why I made it a config option that defaults to
true
(defaults to caching on).I think big instances should cache, but for smaller instances with less funding and resources it makes sense to skip the caching.
This also helps mitigate the risk of people posting CSAM to attack other communities which your instance is subscribed to right? If you instance never cached the image, there’s no clean-up you have to do on your end provided the original instance removes the image from their server.
As you’ve mentioned, it makes sense for larger instances to have a cache, but smaller instance (especially single-user instances) may actually be better off not caching at all and just hosting their own images. As a more long-term solution which can add to this patch, it would be good if Lemmy did 2 things: