Yes. FWIW, as of a few minutes ago when I cloned this one, all the non-git files have the same hashes as the copy of the original I cloned when it was still up.
(to clarify, I wasn't talking about any git-specific hashes, just regular sha2/blake2b hashes of python, json, and font files. However, the two sha1 commit hashes in the git history match as well.)
This is a weird thing with how GitHub forks work. All the objects within a fork network are stored within a global namespace, so you can change the repository name in the URL and find objects that appear to belong to one repository despite being unique to a fork.
Is this the code? https://github.com/gudvardur/amazon_book_downloader
Yes. FWIW, as of a few minutes ago when I cloned this one, all the non-git files have the same hashes as the copy of the original I cloned when it was still up.
(to clarify, I wasn't talking about any git-specific hashes, just regular sha2/blake2b hashes of python, json, and font files. However, the two sha1 commit hashes in the git history match as well.)
This is a weird thing with how GitHub forks work. All the objects within a fork network are stored within a global namespace, so you can change the repository name in the URL and find objects that appear to belong to one repository despite being unique to a fork.
These commit sha's do not match the original:
4526863 - Initial commit
4 replies →