I’ve been toying with a few items the last few months, and now they’re active. The filemanager now crosschecks the files against my stored MD5 hashes, and will report if a file may have become damaged between my upload and the resulting program on my software page.

As a corollary, this does increase the load on the webserver by an insignificant amount. To help combat this; I’ve made my filemanager caching, so it will store the last hit, if within the last few minutes, compare them to what it computes, and if nothing has changed, it will then send the prior page, rather than recreating the entire page and heirachy.

Pretty cool, huh?

[Edit: I’ve changed the way the output is generated; rather than displaying the check mark next to ‘known good’ files, it will alert the end user when they attempt to download the file if it does not match checksums. This is less astetically pleasing – losing a few geek points for a silent dynamic test, but is much easier on the server.]