5 ms·

> but it also means you can't send a file filled with 0's. To be clear, this can't support a file that contains a block worth of 0s anywhere in the file? That

by setr 6y ago

> but it also means you can't send a file filled with 0's. To be clear, this can't support a file that contains a block worth of 0s anywhere in the file? That seems like a severe limitation Although, the recepient should have encrypted blocks, right? So its only when the output of the hash is all 0's that it should conflict with the resumption algorithm

qrv3w 6y ago
> but it also means you can't send a file filled with 0's. I think I was sleepy because I errored in saying that. You can send a file with 0's without a problem. The only little bug is if you resume a transfer of a file that is filled with zeros then the recipient will re-request blocks it already has (because they are zeros) so that parts of the file get sent twice (worst-case scenario). It is a bug, but a small one IMO that has never manifested in my reality (via issues or my own use). Happy to accept PRs to fix it though!