So when you have a correction in the image urls, for example broken image urls from LC that gets reported or fixed then refreshed for a new scrape for AtlasDB.
This example title had bad image urls that loaded in a 404 error but has now been fixed on the LC side.
Refreshed the scrape on AtlasDB and the AtlasDB site lists the correct image urls and those all load well.
Example title in question: https://lewdcorner.com/threads/11782/
Now the CLIENT in the other hand does not load any of the images at all even though update files has been pushed out.
Seems the old broken image urls stays in the client.
Manually refreshing the media and forcing a redownload on the specific title does not help at all.
So when you have a correction in the image urls, for example broken image urls from LC that gets reported or fixed then refreshed for a new scrape for AtlasDB.
This example title had bad image urls that loaded in a 404 error but has now been fixed on the LC side.
Refreshed the scrape on AtlasDB and the AtlasDB site lists the correct image urls and those all load well.
Example title in question: https://lewdcorner.com/threads/11782/
Now the CLIENT in the other hand does not load any of the images at all even though update files has been pushed out.
Seems the old broken image urls stays in the client.
Manually refreshing the media and forcing a redownload on the specific title does not help at all.