Interesting
Discussion
Note that on services that cache the image and rewrite the output like snort.social, the concept breaks down.
Unless they periodically check the source and update their cache. At best they honor cache settings on the source resource and are just lagged. At worst, users get the wrong experience.
As long as snort social rewrites user content like this I don't recommend it for anything other than referencing notes by url.
Checking now and it is still in my Damus cache..
To work well, we would have to work with the clients to ‘delete that cached image’ if the user hit the delete button..
If someone never saw it in the first place, it never would have been cached..
Still an interesting concept..