By "random" I do not mean that the frequency of the appearance of each image is the same (it's the random number generator on the server. I can't really mess with that).
By "random" I mean that the randomizer will generate a new image every time the page that it is on is loaded (if you navigate away from the page then navigate back, or navigate from one page with the randomizer to another page with the same randomizer), as opposed to generating it only every time the page is reloaded (F5 or clicking refresh).
Before this adjustment, the page had to be reloaded for the randomizer to generate a new image (on most browsers).
The catch: The image must be uploaded to my server using the integrated image uploader. This allows the ASP.NET methods which open the file (which replaces the redirect) to work. Those functions will only work properly for pages that are on my server. If you use your own host, your randomizer will still work, it just won't be completely "random". This limitation is not set by me, but set by the way these methods work.
So, it is still your own decision of where to host, but I am just putting this out there that the randomizer will work better when the images are uploaded to my server
