You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
How does Arweave differ from a personal data space?
Separate a permanent-storage objective from everyday application data management.
Arweave is designed for long-term, permanent retention of submitted data. Its network organizes copies, storage-related proofs and consensus. The permaweb is the ecosystem of content and applications built on that persistent data.
Consider public research material that people must cite over time. Retaining an original is useful, while readers still need a working gateway and application. When a correction is added, distinguish the new version, the version an application displays, and older content that may remain available.
A private journal has different requirements: which apps can read it, how changes work, and how deletion and authorization changes are handled. A permanence objective does not answer those questions. Compare Arc Space, IPFS, Filecoin and Arweave by the problems they address, not simply by their involvement with files. A protocol’s retention objective is not an unconditional availability promise for every access gateway.
Sources and further reading
Check your understanding
Does hiding a record in an app delete it from a permanent-storage network?
That does not follow. Application views and underlying retention are different layers.
Continue along a learning path
- Understand personal data spacesStep 7 of 8