#[3] what is this wizardry, can we stop it?
Discussion
I don't see anything, probably its your browser cache
Good, so delete works if you haven’t seen the image yet.
Curious how you cache images, do you copy and leave on imgproxy.snort? How long?
If we sent you a request to ‘delete’, could you remove the cache?
I have a few layers of cache so its hard to know, Primary cache is the CF Cache Reserve, idk how often it will check origin to see if the file is still alive
Do you have control of it, could you delete it possibly if received a request?
Not sure, maybe we can test one?
Can you delet what #[2] pasted?
Hey, that’s my content. I didn’t give you permission to delete it. 😂
This is an image hosted on void.cat though
So do you do this automatically, or did #[2] copy my nostr.build image and upload to void.cat?
It’s probably undeleteable. I uploaded that using a pair of Nostr keys on Snort that I intentionally lost. 😁
I run void.cat so its possible for me to delete it
Damnit!
🎚️
🙏🏻
So you did manually copy and upload it. Here we are thinking #[2] had some super cache process saving thinks on his void.cat…
I’m still likening the delete idea. If cache is our only challenge, that doesn’t apply to people who haven’t seen it yet.