archive-program

The solution there is for somebody to contribute a translation, even if they can't contribute a list of sources. TheTechTree.md is comparatively new compared to the other files, as can be seen from the history: https://github.com/github/archive-program/commits/master/The... Context like this matters.

This is the guide to read the data: https://github.com/github/archive-program/blob/master/GUIDE.... You need to know how tar, lzma, utf-8 and git work. Judging by how hard it is to decipher ancient texts, I'd be surprised if anybody was able to read code without additional information on these subjects. Especially storing the binary git repo as-is will make it very hard.

There's no git usage, they're just storing a snapshot of each repo's current HEAD in a TAR file (and then compressed and QR-encoded). > The snapshot will consist of the HEAD of the default branch of each repository, minus any binaries larger than 100KB in size—depending on available space, repos with more stars may retain binaries. Each repository will be packaged as a single TAR file. The guide included on each reel about how to access the data is public, git isn't involved in the process: https://github.com/github/archive-program/blob/master/GUIDE....

Rather more eloquently asked than by the other person I saw querying this[0]! I suspect it's covered under Github's TOS - specifically[1], only public repositories were included and these are all effectively just backups. Especially in the case of the vault in Svalbard. But you can opt out of the 'warm storage'[0]. [0] https://github.com/github/archive-program/issues/36 [1] https://docs.github.com/en/github/site-policy/github-terms-o...