Attribution - You need to assign the work in the manner specified by the author or licensor (although it never signifies that they will support you or your work).
Sharing - If you modify, transform, or build this work, you may only distribute the work under the same or similar license as this work.
This file contains additional information such as digital cameras, scanners, Exif metadata that may be added by software programs for creation or digitization. If the file has been changed from its original state, details of the original file may not be reflected completely depending on details such as time stamp. The timestamp is as accurate as the camera's clock and may be completely wrong
As many people know, file backups and file sharing in Sia are virtually identical. File sharing can be thought of as providing a backup of a file to a friend. Or you can think of backing up files as sharing files with yourself. We will focus on creating backup endpoints in v1.3.4 and providing basic support for file sharing in v1.3.5. The goal of v1.3.6 is a recursive metadata compression technique that allows it to be small enough to place system-wide backups on the block chain itself. You can encrypt these backups using your seed and put them in a block chain so you can recover the data using something other than the wallet seed. This requires low frequency backup transactions on the chain. In other words, backups will not be done continuously, but this is a big step forward.
The primary purpose of v1.3.4 is to back up files. In today's Sia, if the host is corrupted, all data will be destroyed. The developer (either myself or my co-founder) can recover the file by taking an old backup of the metadata, which is a very professional work by hand. We change it in v1.3.4 so that we can back up the metadata and recover the file on host crash. And eliminate single point of failure most people currently have.