Version 0.59.0

Changed what the server is told about a file's size: the bytes that went to the storage network, not the size of your original file.

Until today the browser told the server the exact byte length of each original file, and that number was written into our database — and it is also not the number anything is paid for, because the storage network charges for the encrypted bytes, which are slightly larger. From now on there is one number, the bytes that were uploaded, and the size of your original file is only in the file list your account encrypts for itself, which we cannot read. This does not hide your file's size on its own: the encrypted length is a fixed amount above the original one, so it can still be worked back. Hiding it means padding what is uploaded, which is a separate change and is not here yet.

Changed the credit price to be charged on the encrypted size, which is what the treasury actually buys.

The credit price used to be worked out from the original file size while the storage was bought with the encrypted size, so the difference was storage nobody paid for. The price is worked out per piece, so a piece whose size is an exact multiple of 1 MB now costs one credit more: the encryption header spills into the next megabyte and that megabyte is bought in full. A 1 MB file goes from 1 credit to 2; a 1.5 MB file does not change; a 5 GB file goes from 5,120 to 5,125. The number shown before you confirm is still exactly the number charged.

Fixed a size limit that would have refused a full-size piece of a large file after it was uploaded and paid for.

A large file is uploaded in pieces of up to 1 GB, and the server's ceiling for one piece was exactly 1 GB — measured on the original size. Once the number became the encrypted size, a full piece was 4,168 bytes over the line. The ceiling now includes the encryption overhead it is measuring.