The cache has been busted: 0 times
The cards on this page are github-readme-stats repo cards (adapted on a fork created and hosted by hesreallyhim in order to show more repo stats). They show the number of open Issues in this repo.
GitHub uses a service called camo for image caching and privacy/anonymization. That means that if you are serving an image with dynamic content1, changes to the content may not be reflected right away. This repo illustrates different approaches to cache-busting so you can see for yourself what works or does not work at the current point in time.
Tip
Create a new Issue in the repo. Do not include the word "nonce" anywhere in the body. See if and when the count on the card is actually updated.
[](https://github.com/hesreallyhim)Tip
The image URL below contains a query parameter nonce with a random number value. Create an Issue in this repository and write the word "nonce" somewhere in the body. This will trigger a GitHub Action that changes the query parameter value to some other "random" number. This is used to test whether changing query parameters is sufficient to bust the cache and refresh the image content.
[](https://github.com/hesreallyhim)Thanks to anuraghazra, a pioneer of README-engineering, and maintainer of github-readme-stats.
Footnotes
-
Nowadays, an "image with dynamic content" is usuaully known as a "movie" (or, if you haven't heard of that, it's sort of like a "TikTok" but not as hilarious)... that's not really what I meant though - I should have said something like "an image that's fetched from a URL that points to a server that changes the contents of the image that being served dynamically." As you can probably tell, I've read many many long books (or, if you haven't heard of that, it's sort of like a "post" but not as profound). ↩