>>100
I thought that, but as it's an archive they will be largely static. Unless one runs a normalisation or silence-stripping pass over everything, there will only be one copy of anything.
The idea makes use of the distributed properties of git, or maybe fossil, which would provide better availability than FTP or another traditional centralised approach. The version control aspect is more of a nice way to see history, rather than necessary by design.