3 | 3 | Currently, the cloud backend splits shares into "chunks" to limit the amount of data that needs to be held in memory or in a store object (see [source:docs/specifications/backends/raic.rst]). This is somewhat redundant with segmentation: ciphertext "segments" are erasure-encoded into "blocks" (a segment is k = {{{shares.needed}}} times larger than a block), and stored in a share together with a header and metadata, which is then chunked. Blocks and chunks are not aligned (for two reasons: the share header, and the typical block size of 128 KiB / 3, which is not a factor of the 512 KiB default chunk size). So, |