Interesting idea. It would be something to consider... the only issue is that to save disk space, the repository is not currently stored on the local machine. A hashcode could be stored after a completed update, however, and compared to a server hash before the next update, I suppose. The only issue would be that people who overwrote files or deleted files by mistake wouldn\'t be able to get an update without deleting the hashcode for the repository, a process that might confuse them... I don\'t know if it\'s worth it or not; it depends on the load on the update servers.