Images posted within the last 48 hours will appear as broken. This is expected and intended.
Yesterday 2023-08-27 a community on the lemmy.world instance received multiple posts containing CSAM (or as it is more commonly known CP) content, which spread throughout the federation. We also ended up becoming involuntary hosts of said content.
Due to the severely limited nature of the Lemmy moderation tools, removing or purging the incriminated posts from the admin UI wasn’t sufficient and didn’t cause the images to be actually removed from our server. Because of this, a nuclear option was required. I have deleted every image saved by our server during the last 48 hours.
Unfortunately this also includes a post on !pcm@lemmy.basedcount.com , as well as multiple posts on !returntomonke@lemmy.basedcount.com. Authors of the affected posts can fix them by re-uploading their images, without the need to recreate the posts.
We are sorry for the inconvenience, but hosting CSAM content is highly illegal and we simply can’t take any risks on this front.
I am currently discussing with the other admins whether further measures are necessary, to prevent this from happening in the future. We’ll keep you posted if we have any updates.
EDIT [2023-08-28 10:00 UTC]:
The attack is still ongoing. I have now blocked the community and further deleted the last 15 minutes of images.
The two quotes of mine are functionally equivalent. Not caching data and delivering from the source on request are the same thing.
From the way you worded it I understood it as:
which aren’t the same thing, two different people making the same choice