What are the chances of someone tweaking build scripts on sourceforge, so that in addition to sha sums, torrent, signature files, you also host a zsync file for each ISO, or such like? I’d like to torrent seed your distro’s most popular images to facilitate delivery, but the size of the download for each new point release is daunting. With zsync you can at least take some advantage of how there’s an older download image locally (still have official 22.0 images on hand), that effectively can somewhat reduce the size of the network transfer needed to update install files. In debian, there’s something similar to zsync called jigdo, to reduce ISO download volume, lightening the load on ftp servers. Thoughts?
Sorry I was unclear about intent. The idea was not so much automating the newly downloaded image verification, it was about reducing download traffic needed to complete the new local image. When I seed torrents, I mostly acquire the payload by means other than bittorrent/wget: jigdo, zsync, or similar, so that older local images can be put to good use in making large size images not so download intensive.