Correct torrent magnet in the README - #28
Merged
Merged
Conversation
The torrent was generated with mktorrent using its default piece length of 256 Kb. That default is fine for a few GB; it is not fine for a TB payload: the torrent stores one 20-byte SHA-1 per piece, so 4,018,567 pieces produce ~80 MB of hashes in the info dictionary alone. That breaks libtorrent-based clients. So I regenerated another one with 16 MiB pieces. This eases, but does not answer, sqliteai#24: it is still a torrent, and the ask there is an IPFS or plain-HTTP mirror for users who cannot reach BitTorrent at all.
Member
|
Thanks a lot @pierre-x |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The torrent was generated with mktorrent using its default piece length of 256 Kb. That default is fine for a few GB; it is not fine for a TB payload: the torrent stores one 20-byte SHA-1 per piece, so 4,018,567 pieces produce ~80 MB of hashes in the info dictionary alone. That breaks libtorrent-based clients.
So I regenerated another one with 16 MiB pieces.
This eases, but does not answer, #24: it is still a torrent, and the ask there is an IPFS or plain-HTTP mirror for users who cannot reach BitTorrent at all.