Maybe things become clearer if I explain "volatile" in programming. It boils down to a file/variable shared by multiple independent processes.
As you may have noticed, the python file is the only file attached to the page. All the images are not actually saved on site, but are on Wikimedia servers. That means were Wikimedia to remove them, they would disappear from the gallery. Non of the files were downloaded or uploaded by me. The page just links to them. This has the benefit that the source can easily be verified if the image is downloaded and used in CI articles. It also removes the file size limit of the page as links are far lighter than actual image files.
I do admit that an empty chessboard is more orderly than a full one and sorting through it is much easier for the chess player. An empty gallery has something appealing, but I don't believe it is what people come in search for.
I do appreciate that you looked at it. I almost thought my little project would just stay unnoticed.
Ps: What happened to your inbox? 1748 unread messages is a bit excessive.
EDIT: This post is a reply to the original post. It does not make sens if tried to be read as a response to what is now above it.
EDIT 2: Apparently Wikipedia disagrees with how I use volatile statements.
Furthermore, in C and C++ it does not work in most threading scenarios, and that use is discouraged.
So it works in some scenarios and can be used. Just pointing this out before someone notices.