you guys realize that all images on imglite.pro starts with NY2lH, then has some pseudo random string after it, right? if it’s a big enough service they’re going to run into conflicts later down the line, and they’re going to have scenarios like this. i doubt boltster posted pony research, and i’m fairly certain that it’s a image host conflict. you can have situations like this where the server sided cache has not been updated (Cloudflare has SO MANY issues with this, especially JavaScript.), and there’s no way to force purge it from your client.
yes, it’s an unfortunate circumstance, and it can happen. please do some research on server sided caches before thinking that a client side purge will force something like Cloudflare to update their cache. that’s not how it works, and if it worked that way, you would have a way to force Cloudflare to spam requests to their server, which isn’t good
smh